mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] cross-nasm: Version bump. 3.01 -> 3.02
Date: Fri, 10 Jul 2026 08:21:11 +0200	[thread overview]
Message-ID: <20260710062111.492821-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260630180357.3503989-1-christian.melki@t2data.com>

Thanks, applied as 00e0f21a452042acf5b19aa6d754c876ea12be89.

Michael

[sent from post-receive hook]

On Fri, 10 Jul 2026 08:21:11 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor bugfix release.
> https://www.nasm.us/docs/3.02/nasmac.html
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260630180357.3503989-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 4f1e06a6a9ab..f6900684592b 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	:= 3.01
> +CROSS_NASM_VERSION	:= 3.02
>  ifdef PTXCONF_ARCH_X86
> -CROSS_NASM_SHA256	:= b7324cbe86e767b65f26f467ed8b12ad80e124e3ccb89076855c98e43a9eddd4
> +CROSS_NASM_SHA256	:= 87336eba53b4acfe917424ab5d500d2b0054d9f5148d35c2273ccf2cfb712f0d
>  CROSS_NASM		:= nasm-$(CROSS_NASM_VERSION)
>  CROSS_NASM_SUFFIX	:= tar.xz
>  CROSS_NASM_URL		:= \



      reply	other threads:[~2026-07-10  6:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 18:03 [ptxdist] [PATCH] " Christian Melki
2026-07-10  6:21 ` 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=20260710062111.492821-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