From: Jarkko Sakkinen <jarkko@kernel.org>
To: 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,
Thorsten Blum <thorsten.blum@linux.dev>
Subject: [GIT PULL] KEYS: keys-next-6.19-rc1
Date: Fri, 28 Nov 2025 00:36:22 +0200 [thread overview]
Message-ID: <aSjSZj47-p_3i_Xn@kernel.org> (raw)
The following changes since commit e1afacb68573c3cd0a3785c6b0508876cd3423bc:
Merge tag 'ceph-for-6.18-rc8' of https://github.com/ceph/ceph-client (2025-11-27 11:11:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/keys-next-6.19-rc1
for you to fetch changes up to 8c8e3df3d2f51e9a3f6f1a1112adf250f7652d42:
keys: Fix grammar and formatting in 'struct key_type' comments (2025-11-27 23:56:58 +0200)
----------------------------------------------------------------
Hi,
This first pull request for keys contains only three fixes.
BR, Jarkko
----------------------------------------------------------------
Thorsten Blum (3):
keys: Remove redundant less-than-zero checks
keys: Replace deprecated strncpy in ecryptfs_fill_auth_tok
keys: Fix grammar and formatting in 'struct key_type' comments
include/linux/key-type.h | 9 ++++++---
security/keys/big_key.c | 2 +-
security/keys/encrypted-keys/ecryptfs_format.c | 3 +--
security/keys/encrypted-keys/encrypted.c | 4 ++--
security/keys/trusted-keys/trusted_core.c | 4 ++--
security/keys/user_defined.c | 2 +-
6 files changed, 13 insertions(+), 11 deletions(-)
next reply other threads:[~2025-11-27 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 22:36 Jarkko Sakkinen [this message]
2025-12-03 19:32 ` [GIT PULL] KEYS: keys-next-6.19-rc1 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=aSjSZj47-p_3i_Xn@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=thorsten.blum@linux.dev \
--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