mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH 1/2] fixup! arch: sync READ_ONCE/WRITE_ONCE with Linux
Date: Mon, 2 Jun 2025 15:58:56 +0200	[thread overview]
Message-ID: <f0da685b-4f01-43b7-8039-7e966fe3c64b@pengutronix.de> (raw)
In-Reply-To: <174846302090.3937553.13526862967830100532.b4-ty@pengutronix.de>

Hello Sascha,

On 28.05.25 22:10, Sascha Hauer wrote:
> 
> On Wed, 28 May 2025 13:30:49 +0200, Ahmad Fatoum wrote:
>> The __no_kasan_or_inline attribute is already defined in <linux/compiler.h>.
>> Drop it from the header here and do the replacement in its own commit.
>>
>>
> 
> Applied, thanks!
> 
> [1/2] fixup! arch: sync READ_ONCE/WRITE_ONCE with Linux
>       https://git.pengutronix.de/cgit/barebox/commit/?id=c6b626c4eed6 (link may not be stable)
> [2/2] compiler: check for __SANITIZE_ADDRESS__ instead of CONFIG_KASAN
>       https://git.pengutronix.de/cgit/barebox/commit/?id=0d321ab1a307 (link may not be stable)

I am missing these in next.

Thanks,
Ahmad

> 
> Best regards,


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-06-02 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 11:30 Ahmad Fatoum
2025-05-28 11:30 ` [PATCH 2/2] compiler: check for __SANITIZE_ADDRESS__ instead of CONFIG_KASAN Ahmad Fatoum
2025-05-28 20:10 ` [PATCH 1/2] fixup! arch: sync READ_ONCE/WRITE_ONCE with Linux Sascha Hauer
2025-06-02 13:58   ` Ahmad Fatoum [this message]
2025-06-02 14:24     ` Ahmad Fatoum

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=f0da685b-4f01-43b7-8039-7e966fe3c64b@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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