mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] sandbox: setjmp: avoid conflict with noinline macro
Date: Mon, 01 Dec 2025 10:56:48 +0100	[thread overview]
Message-ID: <176458300808.150585.12114505184577510660.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251128104258.1748758-1-a.fatoum@pengutronix.de>


On Fri, 28 Nov 2025 11:42:57 +0100, Ahmad Fatoum wrote:
> We define noinline as a macro in <linux/compiler_types.h>, which we
> don't yet include here, but might in future with the Kbuild update.
> 
> Prepare for that by using the double underscore version instead, which
> won't conflict.
> 
> 
> [...]

Applied, thanks!

[1/1] sandbox: setjmp: avoid conflict with noinline macro
      https://git.pengutronix.de/cgit/barebox/commit/?id=2a15cc630f36 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      reply	other threads:[~2025-12-01  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28 10:42 Ahmad Fatoum
2025-12-01  9:56 ` Sascha Hauer [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=176458300808.150585.12114505184577510660.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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