From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] nasm: Version bump. 2.16.03 -> 3.01
Date: Thu, 15 Jan 2026 16:12:09 +0100 [thread overview]
Message-ID: <20260115151209.231204-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251226163157.3322128-1-christian.melki@t2data.com>
Thanks, applied as 2ccc305b4018fd3dcf79197e7276d7bc604c5fce.
Michael
[sent from post-receive hook]
On Thu, 15 Jan 2026 16:12:09 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Looks bigger by the numbers than it actually is.
> Some new insns and bug fixes.
>
> https://www.nasm.us/docs/3.00/nasmac.html
> https://www.nasm.us/docs/3.01/nasmac.html
>
> * License hash changed. License info was SPDX-ified.
> No change to actual license.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251226163157.3322128-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/cross-nasm.make b/rules/cross-nasm.make
> index ea419af71f87..ca0cd62bbe0e 100644
> --- a/rules/cross-nasm.make
> +++ b/rules/cross-nasm.make
> @@ -15,9 +15,9 @@ CROSS_PACKAGES-$(PTXCONF_CROSS_NASM) += cross-nasm
> #
> # Paths and names
> #
> -CROSS_NASM_VERSION := 2.16.03
> +CROSS_NASM_VERSION := 3.01
> ifdef PTXCONF_ARCH_X86
> -CROSS_NASM_MD5 := 2b8c72c52eee4f20085065e68ac83b55
> +CROSS_NASM_MD5 := 8414016d6ad0e113958c29066dfcc550
> CROSS_NASM := nasm-$(CROSS_NASM_VERSION)
> CROSS_NASM_SUFFIX := tar.xz
> CROSS_NASM_URL := \
> @@ -27,7 +27,7 @@ CROSS_NASM_SOURCE := $(SRCDIR)/$(CROSS_NASM).$(CROSS_NASM_SUFFIX)
> CROSS_NASM_DIR := $(CROSS_BUILDDIR)/$(CROSS_NASM)
> CROSS_NASM_LICENSE := BSD-2-Clause
> CROSS_NASM_LICENSE_FILES := \
> - file://LICENSE;md5=90904486f8fbf1861cf42752e1a39efe
> + file://LICENSE;md5=6178dc4f5355e40552448080e67a214b
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-01-15 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 16:31 [ptxdist] [PATCH] " Christian Melki
2026-01-15 15:12 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260115151209.231204-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox