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. 2.15.05 -> 2.16.01
Date: Wed, 12 Apr 2023 08:29:44 +0200 [thread overview]
Message-ID: <20230412062944.3434976-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230329181939.639857-1-christian.melki@t2data.com>
Thanks, applied as 90406cb75e6d3dd97eeb1bd9e3df9a3db015a957.
Michael
[sent from post-receive hook]
On Wed, 12 Apr 2023 08:29:44 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Various bugs and fixes.
> RDOFF support (nasm only format) has been removed.
> https://nasm.us/doc/nasmdocc.html
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230329181939.639857-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 4ad4407e8420..c84e97d18aa6 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.15.05
> +CROSS_NASM_VERSION := 2.16.01
> ifdef PTXCONF_ARCH_X86
> -CROSS_NASM_MD5 := 1c9802446d7341c41c21eb98c7859064
> +CROSS_NASM_MD5 := d755ba0d16f94616c2907f8cab7c748b
> CROSS_NASM := nasm-$(CROSS_NASM_VERSION)
> CROSS_NASM_SUFFIX := tar.xz
> CROSS_NASM_URL := http://www.nasm.us/pub/nasm/releasebuilds/$(CROSS_NASM_VERSION)/$(CROSS_NASM).$(CROSS_NASM_SUFFIX)
prev parent reply other threads:[~2023-04-12 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 18:19 [ptxdist] [PATCH] " Christian Melki
2023-04-12 6:29 ` 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=20230412062944.3434976-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