[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c9924ca8c93182d8673064cd02262b75857fe67.camel@linux.ibm.com>
Date: Thu, 30 Jun 2022 09:21:55 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Palmer Dabbelt <palmer@...osinc.com>, dmitry.kasatkin@...il.com,
linux-integrity@...r.kernel.org
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V
Hi Palmer,
On Thu, 2022-06-23 at 21:48 -0700, Palmer Dabbelt wrote:
> This rolled itself back to the top of my inbox, so I figured I'd send it
> again as Rob's review landed. IMO the security/integrity/ima/ change is
> sufficiently trivial that it's fine to take it through the RISC-V tree
> but I don't have an Review/Ack so I'll wait until this loops back again
> to give the security/integrity/ folks a chance to chime in.
>
> If this loops back to the top of my queue (which looks about a month
> deep right now) without any comments then I'll put it in riscv/for-next.
>
> Thanks!
>
> Changes since v1
> <https://lore.kernel.org/all/20220520154430.18593-1-palmer@rivosinc.com/>
> * Collected reviews for drivers/of/kexec.c.
Maybe better that you upstream the RISC-V changes. So far there aren't
any merge conflicts with this patchset, but a number of other kexec
patch sets will hopefully be upstreamed in the coming open window. I'd
appreciate if you could create a topic branch for the first two
patches.
thanks,
Mimi
Powered by blists - more mailing lists