From: Rob Herring <robh@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: lizhengyu3@huawei.com, Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
aou@eecs.berkeley.edu, frowand.list@gmail.com,
zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
jmorris@namei.org, serge@hallyn.com, liaochang1@huawei.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, linux@rivosinc.com
Subject: Re: [PATCH v1 1/5] drivers: of: kexec ima: Support 32-bit platforms
Date: Fri, 20 May 2022 17:42:45 -0500 [thread overview]
Message-ID: <20220520224245.GA385188-robh@kernel.org> (raw)
In-Reply-To: <20220520154430.18593-2-palmer@rivosinc.com>
On Fri, May 20, 2022 at 08:44:27AM -0700, Palmer Dabbelt wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> RISC-V recently added kexec_file() support, which uses enables kexec
> IMA. We're the first 32-bit platform to support this, so we found a
> build bug.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> drivers/of/kexec.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Assuming you don't want me to apply it:
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-20 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 15:44 [PATCH v1 0/5] Support kexec_file on 32-bit RISC-V Palmer Dabbelt
2022-05-20 15:44 ` [PATCH v1 1/5] drivers: of: kexec ima: Support 32-bit platforms Palmer Dabbelt
2022-05-20 22:42 ` Rob Herring [this message]
2022-05-20 15:44 ` [PATCH v1 2/5] ima: Fix a build issue on " Palmer Dabbelt
2022-05-20 15:44 ` [PATCH v1 3/5] RISC-V: kexec: Use Elf64 on 64-bit targets Palmer Dabbelt
2022-05-20 15:44 ` [PATCH v1 4/5] RISC-V: purgatory: Use XLEN-length loads to support rv32 Palmer Dabbelt
2022-05-20 15:44 ` [PATCH v1 5/5] RISC-V: Allow kexec_file() on 32-bit platforms Palmer Dabbelt
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=20220520224245.GA385188-robh@kernel.org \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=frowand.list@gmail.com \
--cc=jmorris@namei.org \
--cc=liaochang1@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@rivosinc.com \
--cc=lizhengyu3@huawei.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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).