From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org, linux-toolchains@vger.kernel.org,
Vignesh Balasubramanian <vigbalas@amd.com>
Cc: Kees Cook <keescook@chromium.org>,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, aneesh.kumar@kernel.org,
naveen.n.rao@linux.ibm.com, ebiederm@xmission.com,
x86@kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-mm@kvack.org, bpetkov@amd.com, jinisusan.george@amd.com,
matz@suse.de, binutils@sourceware.org, jhb@FreeBSD.org,
felix.willgerodt@intel.com
Subject: Re: [PATCH 0/1] Replace the macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig
Date: Mon, 15 Apr 2024 11:03:32 -0700 [thread overview]
Message-ID: <171320421021.253137.15736984105365154364.b4-ty@chromium.org> (raw)
In-Reply-To: <20240412062138.1132841-1-vigbalas@amd.com>
On Fri, 12 Apr 2024 11:51:37 +0530, Vignesh Balasubramanian wrote:
> This patch replaces the macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig
> as discussed here
> https://lore.kernel.org/lkml/CA+55aFxDk9_cmo4SPYMgG_WQ+_g5e_v6O-HEtQ_nTs-q1zjykg@mail.gmail.com/
> It is a pre-requisite patch for the review
> https://lore.kernel.org/lkml/20240314112359.50713-1-vigbalas@amd.com/
> I have split this patch as suggested in the review comment
> https://lore.kernel.org/lkml/87o7bg31jd.fsf@mail.lhotse/
>
> [...]
Applied to for-next/execve, thanks!
[1/1] Replace macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig
https://git.kernel.org/kees/c/a9c3475dd67b
Take care,
--
Kees Cook
prev parent reply other threads:[~2024-04-15 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 6:21 Vignesh Balasubramanian
2024-04-12 6:21 ` [PATCH 1/1] Replace " Vignesh Balasubramanian
2024-04-12 12:07 ` Michael Ellerman
2024-04-22 8:15 ` Florian Weimer
2024-04-15 18:03 ` Kees Cook [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=171320421021.253137.15736984105365154364.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=aneesh.kumar@kernel.org \
--cc=binutils@sourceware.org \
--cc=bpetkov@amd.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ebiederm@xmission.com \
--cc=felix.willgerodt@intel.com \
--cc=jhb@FreeBSD.org \
--cc=jinisusan.george@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matz@suse.de \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=vigbalas@amd.com \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).