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: (subset) [PATCH 1/4] ARM: add ARM32/ARM64 symbols for use in generic code
Date: Wed, 14 Aug 2024 11:13:22 +0200	[thread overview]
Message-ID: <172362680223.1296547.14464614952232456391.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240809141755.312665-1-a.fatoum@pengutronix.de>


On Fri, 09 Aug 2024 16:17:52 +0200, Ahmad Fatoum wrote:
> The CPU_32 and CPU_64 symbols are only defined for ARM, but they are
> still confusing to encounter in common code, because they have no
> explicit reference to ARM. Add ARM32/ARM64 symbols that can be used
> instead.
> 
> 

Applied, thanks!

[1/4] ARM: add ARM32/ARM64 symbols for use in generic code
      https://git.pengutronix.de/cgit/barebox/commit/?id=e490bb32045f (link may not be stable)
[2/4] efi: payload: force PBL_FULLY_PIC for ARM64
      https://git.pengutronix.de/cgit/barebox/commit/?id=95c7524fd756 (link may not be stable)
[3/4] efi: payload: alert user if CONFIG_FS_EFI is missing
      https://git.pengutronix.de/cgit/barebox/commit/?id=12a4d57229ae (link may not be stable)

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




      parent reply	other threads:[~2024-08-14  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 14:17 Ahmad Fatoum
2024-08-09 14:17 ` [PATCH 2/4] efi: payload: force PBL_FULLY_PIC for ARM64 Ahmad Fatoum
2024-08-09 14:17 ` [PATCH 3/4] efi: payload: alert user if CONFIG_FS_EFI is missing Ahmad Fatoum
2024-08-09 14:17 ` [PATCH 4/4] ARM: i.MX8M: neuter initcalls when EFI booted Ahmad Fatoum
2024-08-14  9:14   ` Ahmad Fatoum
2024-08-14  9:13 ` 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=172362680223.1296547.14464614952232456391.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