From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "David Howells" <dhowells@redhat.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
<keyrings@vger.kernel.org>, <linux-integrity@vger.kernel.org>
Subject: Re: [GIT PULL] KEYS: keys-next-6.12-rc7
Date: Wed, 06 Nov 2024 20:38:34 +0200 [thread overview]
Message-ID: <D5FBC0756PMF.3SBC48BP5UTET@kernel.org> (raw)
In-Reply-To: <D5FB9PK9DD35.1B1VBVMPOZPRS@kernel.org>
On Wed Nov 6, 2024 at 8:35 PM EET, Jarkko Sakkinen wrote:
> Couple of fixes for keys and trusted keys. For me it id not make
> (common) sense to separate them into separate them into separate keys
> and trusted keys PR's.
oops, sorry for the typos ;-)
BR, Jarkko
next prev parent reply other threads:[~2024-11-06 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:35 [GIT PULL] KEYS: keys-next-6.12-rc7 Jarkko Sakkinen
2024-11-06 18:38 ` Jarkko Sakkinen [this message]
2024-11-06 19:38 ` pr-tracker-bot
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=D5FBC0756PMF.3SBC48BP5UTET@kernel.org \
--to=jarkko@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox