From: Nathan Chancellor <nathan@kernel•org>
To: Mimi Zohar <zohar@linux•ibm.com>
Cc: Arnd Bergmann <arnd@kernel•org>,
Madhavan Srinivasan <maddy@linux•ibm.com>,
Michael Ellerman <mpe@ellerman•id.au>,
Heiko Carstens <hca@linux•ibm.com>,
Vasily Gorbik <gor@linux•ibm.com>,
Alexander Gordeev <agordeev@linux•ibm.com>,
Arnd Bergmann <arnd@arndb•de>,
Roberto Sassu <roberto.sassu@huawei•com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail•com>,
Paul Moore <paul@paul-moore•com>,
James Morris <jmorris@namei•org>,
"Serge E. Hallyn" <serge@hallyn•com>,
Jarkko Sakkinen <jarkko@kernel•org>,
Ard Biesheuvel <ardb@kernel•org>, Coiby Xu <coxu@redhat•com>,
Nicholas Piggin <npiggin@gmail•com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel•org>,
Christian Borntraeger <borntraeger@linux•ibm.com>,
Sven Schnelle <svens@linux•ibm.com>,
Eric Snowberg <eric.snowberg@oracle•com>,
Nick Desaulniers <nick.desaulniers+lkml@gmail•com>,
Bill Wendling <morbo@google•com>,
Justin Stitt <justinstitt@google•com>,
Andrew Donnellan <ajd@linux•ibm.com>,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org,
linux-s390@vger•kernel.org, linux-arch@vger•kernel.org,
linux-integrity@vger•kernel.org,
linux-security-module@vger•kernel.org, keyrings@vger•kernel.org,
llvm@lists•linux.dev
Subject: Re: [PATCH] integrity: avoid using __weak functions
Date: Mon, 9 Mar 2026 14:29:47 -0700 [thread overview]
Message-ID: <20260309212947.GA4150408@ax162> (raw)
In-Reply-To: <abb4d186d1ca76c080d5e15bcd9e0019cce3af39.camel@linux.ibm.com>
On Sun, Mar 08, 2026 at 09:01:58PM -0400, Mimi Zohar wrote:
> Thanks Arnd, Nathan. LGTM. Nathan, could you send a patch with a proper patch
> description.
Done, thanks for the input!
https://lore.kernel.org/20260309-integrity-drop-weak-arch-get-secureboot-v1-1-6460d5c4bb89@kernel.org/
Cheers,
Nathan
prev parent reply other threads:[~2026-03-09 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 15:03 [PATCH] integrity: avoid using __weak functions Arnd Bergmann
2026-03-06 22:56 ` Nathan Chancellor
2026-03-06 23:28 ` Arnd Bergmann
2026-03-09 1:01 ` Mimi Zohar
2026-03-09 21:29 ` Nathan Chancellor [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=20260309212947.GA4150408@ax162 \
--to=nathan@kernel$(echo .)org \
--cc=agordeev@linux$(echo .)ibm.com \
--cc=ajd@linux$(echo .)ibm.com \
--cc=ardb@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=arnd@kernel$(echo .)org \
--cc=borntraeger@linux$(echo .)ibm.com \
--cc=chleroy@kernel$(echo .)org \
--cc=coxu@redhat$(echo .)com \
--cc=dmitry.kasatkin@gmail$(echo .)com \
--cc=eric.snowberg@oracle$(echo .)com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=jarkko@kernel$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=justinstitt@google$(echo .)com \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-integrity@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=maddy@linux$(echo .)ibm.com \
--cc=morbo@google$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=nick.desaulniers+lkml@gmail$(echo .)com \
--cc=npiggin@gmail$(echo .)com \
--cc=paul@paul-moore$(echo .)com \
--cc=roberto.sassu@huawei$(echo .)com \
--cc=serge@hallyn$(echo .)com \
--cc=svens@linux$(echo .)ibm.com \
--cc=zohar@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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