From: Palmer Dabbelt <palmer@rivosinc.com> To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, linux-integrity@vger.kernel.org Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Subject: [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V Date: Thu, 23 Jun 2022 21:48:06 -0700 [thread overview] Message-ID: <20220624044811.9682-1-palmer@rivosinc.com> (raw) 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.
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com> To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, linux-integrity@vger.kernel.org Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Subject: [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V Date: Thu, 23 Jun 2022 21:48:06 -0700 [thread overview] Message-ID: <20220624044811.9682-1-palmer@rivosinc.com> (raw) 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. _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-06-24 4:50 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-24 4:48 Palmer Dabbelt [this message] 2022-06-24 4:48 ` [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V Palmer Dabbelt 2022-06-24 4:48 ` [PATCH v2 1/5] drivers: of: kexec ima: Support 32-bit platforms Palmer Dabbelt 2022-06-24 4:48 ` Palmer Dabbelt 2022-06-30 13:02 ` Mimi Zohar 2022-06-30 13:02 ` Mimi Zohar 2022-06-30 13:20 ` Mimi Zohar 2022-06-30 13:20 ` Mimi Zohar 2022-06-24 4:48 ` [PATCH v2 2/5] ima: Fix a build issue on " Palmer Dabbelt 2022-06-24 4:48 ` Palmer Dabbelt 2022-06-30 13:21 ` Mimi Zohar 2022-06-30 13:21 ` Mimi Zohar 2022-06-24 4:48 ` [PATCH v2 3/5] RISC-V: kexec: Use Elf64 on 64-bit targets Palmer Dabbelt 2022-06-24 4:48 ` Palmer Dabbelt 2022-06-24 4:48 ` [PATCH v2 4/5] RISC-V: purgatory: Use XLEN-length loads to support rv32 Palmer Dabbelt 2022-06-24 4:48 ` Palmer Dabbelt 2022-06-24 4:48 ` [PATCH v2 5/5] RISC-V: Allow kexec_file() on 32-bit platforms Palmer Dabbelt 2022-06-24 4:48 ` Palmer Dabbelt 2022-06-30 13:21 ` [PATCH v2 0/5] Support kexec_file on 32-bit RISC-V Mimi Zohar 2022-06-30 13:21 ` Mimi Zohar
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=20220624044811.9682-1-palmer@rivosinc.com \ --to=palmer@rivosinc.com \ --cc=dmitry.kasatkin@gmail.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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.