From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH] ARM: remove unused constructor support
Date: Tue, 06 Jan 2026 08:38:15 +0100 [thread overview]
Message-ID: <176768509556.1939565.6310243733347968376.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260105084604.3288407-1-a.fatoum@barebox.org>
On Mon, 05 Jan 2026 09:46:01 +0100, Ahmad Fatoum wrote:
> CONFIG_CONSTRUCTORS was added alongside KASAN support, but it appears to
> be unused and not necessary for KASAN to work.
>
> While at it, we also remove the legacy CONSTRUCTORS directive that only
> exists in the 32-bit, but not 64-bit ARM linker script.
>
> I suspect that in Linux, constructors are needed for external modules,
> but in barebox, we don't currently make use of it, so it should be safe
> to drop.
>
> [...]
Applied, thanks!
[1/1] ARM: remove unused constructor support
https://git.pengutronix.de/cgit/barebox/commit/?id=cb64ad3ea11b (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-01-06 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 8:46 Ahmad Fatoum
2026-01-06 7:38 ` 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=176768509556.1939565.6310243733347968376.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@barebox.org \
--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