From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: cpu: setupc: relocate BSS in relocate_to_adr()
Date: Sat, 14 Mar 2026 08:50:23 +0100 [thread overview]
Message-ID: <1a321a56-c232-46d6-b274-026a108843b5@pengutronix.de> (raw)
In-Reply-To: <177340064747.208368.4405735321340509838.b4-ty@pengutronix.de>
Hello Sascha,
On 3/13/26 12:17, Sascha Hauer wrote:
>
> On Thu, 12 Mar 2026 20:20:42 +0100, Ahmad Fatoum wrote:
>> When calling relocate_to_adr(), barebox is copied without BSS to a new
>> place. The new BSS region is not necessarily zeroed, but setupc()
>> following relocate_to_adr() will take care of that.
>>
>> With incoming change to make setupc() idempotent, this will become
>> problematic as the variable in .data will indicate that the BSS is
>> zeroed, while the new BSS region isn't actually.
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] ARM: cpu: setupc: relocate BSS in relocate_to_adr()
> https://git.pengutronix.de/cgit/barebox/commit/?id=d443585bcce6 (link may not be stable)
> [2/2] fixup! ARM: setup_c: avoid clearing BSS twice
Please reorder "ARM: cpu: setupc: relocate BSS in relocate_to_adr" before "ARM: setup_c: avoid clearing BSS twice" to keep bisection possible without intermittent breakage.
Thanks,
Ahmad
> (no commit info)
>
> 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 |
prev parent reply other threads:[~2026-03-14 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 19:20 Ahmad Fatoum
2026-03-12 19:20 ` [PATCH 2/2] fixup! ARM: setup_c: avoid clearing BSS twice Ahmad Fatoum
2026-03-13 11:17 ` [PATCH 1/2] ARM: cpu: setupc: relocate BSS in relocate_to_adr() Sascha Hauer
2026-03-14 7:50 ` Ahmad Fatoum [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=1a321a56-c232-46d6-b274-026a108843b5@pengutronix.de \
--to=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