From: Jisheng Zhang <jszhang@kernel.org>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH 0/3] riscv: Align section markers with other archs
Date: Thu, 12 Nov 2026 12:35:18 +0800 [thread overview]
Message-ID: <avVCBs57OqqH7kVI@xhacker> (raw)
In-Reply-To: <20261111164345.4059964-5-ardb+git@google.com>
On Wed, Nov 11, 2026 at 05:43:46PM +0100, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> Patch #3 of this series was sent out as part of a EFI series [0] that
> implements generic support for carrying image info data inside the stub,
> and after Sashiko found another related issue, I decided to break it out
> into this series. IOW, patch #3 is a resend.
>
> The point of these changes is to harmonize all architectures that
> support EFI in terms of the section markers, so that generic zboot code
> can refer to them without arch specific #ifdefs. Other generic tools
> probably benefit from this too.
>
> If the maintainers are onboard with this, kindly put it on a stable
> topic branch so I can refer to it from the EFI tree.
>
> [0] https://lore.kernel.org/all/20261110121731.2728824-12-ardb+git@google.com/
>
> Cc: Paul Walmsley <pjw@kernel.org>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> Cc: Albert Ou <aou@eecs.berkeley.edu>
> Cc: Alexandre Ghiti <alex@ghiti.fr>
> Cc: linux-riscv@lists.infradead.org
For the series:
Reviewed-by: Jisheng Zhang <jszhang@kernel.org>
>
> Ard Biesheuvel (3):
> riscv: Use _stext not _text to denote the start of kernel code
> riscv: Make _text point to the start of the kernel image
> riscv: Rename __init_text_end to __inittext_end like other archs
>
> arch/riscv/include/asm/sections.h | 2 +-
> arch/riscv/kernel/image-vars.h | 2 +-
> arch/riscv/kernel/setup.c | 2 +-
> arch/riscv/kernel/vmlinux.lds.S | 6 +++---
> drivers/firmware/efi/libstub/riscv-stub.c | 2 +-
> 5 files changed, 7 insertions(+), 7 deletions(-)
>
>
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> --
> 2.56.0.611.g1030f0b940-goog
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-11-12 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:43 [PATCH 0/3] riscv: Align section markers with other archs Ard Biesheuvel
2026-11-11 16:43 ` [PATCH 1/3] riscv: Use _stext not _text to denote the start of kernel code Ard Biesheuvel
2026-11-11 16:43 ` [PATCH 2/3] riscv: Make _text point to the start of the kernel image Ard Biesheuvel
2026-11-11 16:43 ` [PATCH 3/3] riscv: Rename __init_text_end to __inittext_end like other archs Ard Biesheuvel
2026-11-12 4:35 ` Jisheng Zhang [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=avVCBs57OqqH7kVI@xhacker \
--to=jszhang@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.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