From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Moore <paul@paul-moore.com>,
David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: Invert FINAL_PUT bit
Date: Thu, 12 Jun 2025 13:32:32 +0300 [thread overview]
Message-ID: <aEqswAc8nkXVAJH7@kernel.org> (raw)
In-Reply-To: <CAHk-=wjY7b0gDcXiecsimfmOgs0q+aUp_ZxPHvMfdmAG_Ex_1Q@mail.gmail.com>
On Wed, Jun 11, 2025 at 10:50:46AM -0700, Linus Torvalds wrote:
> On Tue, 10 Jun 2025 at 17:23, Paul Moore <paul@paul-moore.com> wrote:
> >
> > It doesn't look like this has made its way to Linus.
>
> Bah. It "made it" in the sense that sure, it's in my inbox.
>
> But particularly during the the early merge window I end up heavily
> limiting my emails to pull requests. And then it ended up composted at
> the bottom of my endless pile of emails.
>
> I guess I can still take it if people just say "do it".
>
> Linus
+1 for picking it.
BR, Jarkko
next prev parent reply other threads:[~2025-06-12 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 12:18 [PATCH] KEYS: Invert FINAL_PUT bit David Howells
2025-06-11 0:22 ` Paul Moore
2025-06-11 9:12 ` Herbert Xu
2025-06-11 15:54 ` Paul Moore
2025-06-11 16:47 ` Jarkko Sakkinen
2025-06-11 17:50 ` Linus Torvalds
2025-06-11 18:45 ` David Howells
2025-06-11 18:59 ` Linus Torvalds
2025-06-11 20:38 ` Al Viro
2025-06-11 21:21 ` Linus Torvalds
2025-06-12 10:32 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-03 14:39 [PATCH] KEYS: Reduce smp_mb() calls in key_put() Jarkko Sakkinen
2025-04-30 15:25 ` Jarkko Sakkinen
2025-05-03 22:19 ` David Howells
2025-05-04 0:35 ` Herbert Xu
2025-05-04 5:36 ` [PATCH] KEYS: Invert FINAL_PUT bit Herbert Xu
2025-05-04 7:44 ` David Howells
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=aEqswAc8nkXVAJH7@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=torvalds@linux-foundation.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 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.