From: Palmer Dabbelt <palmer@dabbelt.com>
To: mick@ics.forth.gr, ebiederm@xmission.com, kexec@lists.infradead.org
Cc: linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-kernel@vger.kernel.org, mick@ics.forth.gr
Subject: Re: [PATCH v3 1/5] RISC-V: Add EM_RISCV to kexec UAPI header
Date: Thu, 22 Apr 2021 20:30:45 -0700 (PDT) [thread overview]
Message-ID: <mhng-891ba63b-523a-470d-9e50-a881b9e3dde1@palmerdabbelt-glaptop> (raw)
In-Reply-To: <20210405085712.1953848-2-mick@ics.forth.gr>
On Mon, 05 Apr 2021 01:57:08 PDT (-0700), mick@ics.forth.gr wrote:
> Add RISC-V to the list of supported kexec architecturs, we need to
> add the definition early-on so that later patches can use it.
>
> EM_RISCV is 243 as per ELF psABI specification here:
> https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md
>
> Signed-off-by: Nick Kossifidis <mick@ics.forth.gr>
> ---
> include/uapi/linux/kexec.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/kexec.h b/include/uapi/linux/kexec.h
> index 05669c87a..778dc191c 100644
> --- a/include/uapi/linux/kexec.h
> +++ b/include/uapi/linux/kexec.h
> @@ -42,6 +42,7 @@
> #define KEXEC_ARCH_MIPS_LE (10 << 16)
> #define KEXEC_ARCH_MIPS ( 8 << 16)
> #define KEXEC_ARCH_AARCH64 (183 << 16)
> +#define KEXEC_ARCH_RISCV (243 << 16)
>
> /* The artificial cap on the number of segments passed to kexec_load. */
> #define KEXEC_SEGMENT_MAX 16
This is missing the kexec maintainers, who I've added. I'm happy to
just take this along with the rest of the patch set, as that's probably
easiest. I usually like to get an Ack on this sort of thing, but I'm
just going to speculate that this isn't controversial and put this on
riscv/for-next. LMK if you want me to do something more complicated
like a shared tag, but I see the arm64 stuff went in via the arm64 tree
so I'm assuming this is fine.
Thanks!
next prev parent reply other threads:[~2021-04-23 3:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 8:57 [PATCH v3 0/5] RISC-V: Add kexec/kdump support Nick Kossifidis
2021-04-05 8:57 ` [PATCH v3 1/5] RISC-V: Add EM_RISCV to kexec UAPI header Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt [this message]
2021-04-05 8:57 ` [PATCH v3 2/5] RISC-V: Add kexec support Nick Kossifidis
2021-04-06 18:38 ` Alex Ghiti
2021-04-09 10:19 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 3/5] RISC-V: Improve init_resources Nick Kossifidis
2021-04-06 7:19 ` Geert Uytterhoeven
2021-04-06 8:11 ` Nick Kossifidis
2021-04-06 8:22 ` Geert Uytterhoeven
2021-04-09 10:11 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 4/5] RISC-V: Add kdump support Nick Kossifidis
2021-04-06 18:36 ` Alex Ghiti
2021-04-09 10:21 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 5/5] RISC-V: Add crash kernel support Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-07 7:45 ` [PATCH v3 0/5] RISC-V: Add kexec/kdump support Yixun Lan
2021-04-07 16:29 ` Rob Herring
2021-04-09 10:02 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-23 3:36 ` Nick Kossifidis
2021-04-23 3:48 ` Palmer Dabbelt
2021-04-23 3:53 ` Nick Kossifidis
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=mhng-891ba63b-523a-470d-9e50-a881b9e3dde1@palmerdabbelt-glaptop \
--to=palmer@dabbelt.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=paul.walmsley@sifive.com \
/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;
as well as URLs for NNTP newsgroup(s).