From: David Picard <david.picard@clermont.in2p3.fr>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice
Date: Wed, 18 Mar 2026 16:43:49 +0100 [thread overview]
Message-ID: <63a902c9-b6e0-4f77-9bd8-a104423468fd@clermont.in2p3.fr> (raw)
In-Reply-To: <abq80-X7w9qQgooP@pengutronix.de>
Oh, I'm sorry about that...
David
Le 18/03/2026 à 15:55, Sascha Hauer a écrit :
> On Wed, Mar 18, 2026 at 03:12:23PM +0100, David Picard wrote:
>> Did it help? I can make more tests.
> Thanks, yes it helps.
>
> The patch you tested basically is the same as I reverted, modulo the
> debug prints. So indeed the original patch seems to work. My assumption
> is that you didn't have Ahmads fix applied which is on current master
> now.
>
> So I am going to re-apply this patch. Please let me know if something
> still breaks.
>
> Sascha
>
next prev parent reply other threads:[~2026-03-18 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 7:53 [PATCH v2 0/2] ARM: Avoid to clear bss multiple times Sascha Hauer
2026-03-04 7:53 ` [PATCH v2 1/2] ARM: setupc_32: remove relocation code from setup_c Sascha Hauer
2026-03-04 9:02 ` Ahmad Fatoum
2026-03-11 14:41 ` Ahmad Fatoum
2026-03-11 19:08 ` Sascha Hauer
2026-03-04 7:53 ` [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice Sascha Hauer
2026-03-04 9:05 ` Ahmad Fatoum
2026-03-10 10:44 ` Sascha Hauer
2026-03-16 13:21 ` David Picard
2026-03-17 9:06 ` Sascha Hauer
2026-03-17 9:50 ` David Picard
2026-03-17 12:43 ` David Picard
2026-03-17 15:56 ` Ahmad Fatoum
2026-03-17 16:03 ` David Picard
2026-03-17 16:11 ` Ahmad Fatoum
2026-03-18 7:49 ` David Picard
2026-03-18 8:00 ` Sascha Hauer
2026-03-18 10:06 ` David Picard
2026-03-18 14:12 ` David Picard
2026-03-18 14:55 ` Sascha Hauer
2026-03-18 15:43 ` David Picard [this message]
2026-03-23 13:22 ` David Picard
2026-03-10 10:42 ` [PATCH v2 0/2] ARM: Avoid to clear bss multiple times Sascha Hauer
2026-03-17 10:21 ` Sascha Hauer
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=63a902c9-b6e0-4f77-9bd8-a104423468fd@clermont.in2p3.fr \
--to=david.picard@clermont.in2p3.fr \
--cc=a.fatoum@pengutronix.de \
--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