* [GIT PULL] KEYS: for-next-keys-7.2-rc6
@ 2026-07-27 18:45 Jarkko Sakkinen
2026-07-27 21:22 ` Linus Torvalds
2026-07-27 21:50 ` pr-tracker-bot
0 siblings, 2 replies; 5+ messages in thread
From: Jarkko Sakkinen @ 2026-07-27 18:45 UTC (permalink / raw)
To: Linus Torvalds
Cc: David Howells, Herbert Xu, David S. Miller, keyrings,
linux-integrity, Fabrice Derepas, Michael Bommarito
The following changes since commit 248951ddc14de84de3910f9b13f51491a8cd91df:
Merge tag 'hwmon-for-v7.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (2026-07-21 08:34:39 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/for-next-keys-7.2-rc6
for you to fetch changes up to a82c8a05e86f3f84e09698f65b4515b5d04633f6:
assoc_array: trim the final shortcut word using the current chunk end (2026-07-23 18:23:45 +0300)
----------------------------------------------------------------
Hi
This pull request contains bug fixes discussed in [1] and two fixes
(in one commit) from Fabrice for DCP trusted keys backend..
BR, Jarkko
[1] https://lore.kernel.org/keyrings/amINZJVhEBwxEixP@kernel.org/
----------------------------------------------------------------
Fabrice Derepas (1):
KEYS: trusted: dcp: fix key_len validation and calc_blob_len() return type
Michael Bommarito (3):
keys: fix out-of-bounds read in keyring_get_key_chunk()
keys: make keyring key-chunk byte order agree with keyring_diff_objects()
assoc_array: trim the final shortcut word using the current chunk end
lib/assoc_array.c | 3 ++-
security/keys/keyring.c | 14 ++++++++------
security/keys/trusted-keys/trusted_dcp.c | 15 +++++++++++----
3 files changed, 21 insertions(+), 11 deletions(-)
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [GIT PULL] KEYS: for-next-keys-7.2-rc6 2026-07-27 18:45 [GIT PULL] KEYS: for-next-keys-7.2-rc6 Jarkko Sakkinen @ 2026-07-27 21:22 ` Linus Torvalds 2026-07-28 0:49 ` Jarkko Sakkinen 2026-07-27 21:50 ` pr-tracker-bot 1 sibling, 1 reply; 5+ messages in thread From: Linus Torvalds @ 2026-07-27 21:22 UTC (permalink / raw) To: Jarkko Sakkinen Cc: David Howells, Herbert Xu, David S. Miller, keyrings, linux-integrity, Fabrice Derepas, Michael Bommarito On Mon, 27 Jul 2026 at 11:46, Jarkko Sakkinen <jarkko@kernel.org> wrote: > > This pull request contains bug fixes discussed in [1] and two fixes > (in one commit) from Fabrice for DCP trusted keys backend.. Please don't explain commits with links. The commit log is supposed to be legible without a network connection. Links are ok as supplements and background information, but not as a "this is explained by link". And the pull request is supposed to have what I can useas that commit log (either in the email or in the tag). Yes, I edit things for clarity and consistency, but I don't want to follow links and try to figure out what some discussion was all about. So please give me an explanation for what you are asking me to pull. Both so that I see what I'm pulling, and so that I'll have a merge message explaining things for later. I've done this myself this time, but please make your pull requests legible in the future. The patch series you merged even had a cover letter, please keep track of these things and don't make people search for them. Linus ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] KEYS: for-next-keys-7.2-rc6 2026-07-27 21:22 ` Linus Torvalds @ 2026-07-28 0:49 ` Jarkko Sakkinen 2026-07-28 0:50 ` Jarkko Sakkinen 0 siblings, 1 reply; 5+ messages in thread From: Jarkko Sakkinen @ 2026-07-28 0:49 UTC (permalink / raw) To: Linus Torvalds Cc: David Howells, Herbert Xu, David S. Miller, keyrings, linux-integrity, Fabrice Derepas, Michael Bommarito On Mon, Jul 27, 2026 at 02:22:47PM -0700, Linus Torvalds wrote: > On Mon, 27 Jul 2026 at 11:46, Jarkko Sakkinen <jarkko@kernel.org> wrote: > > > > This pull request contains bug fixes discussed in [1] and two fixes > > (in one commit) from Fabrice for DCP trusted keys backend.. > > Please don't explain commits with links. The commit log is supposed to > be legible without a network connection. Links are ok as supplements > and background information, but not as a "this is explained by link". > > And the pull request is supposed to have what I can useas that commit > log (either in the email or in the tag). Yes, I edit things for > clarity and consistency, but I don't want to follow links and try to > figure out what some discussion was all about. > > So please give me an explanation for what you are asking me to pull. > Both so that I see what I'm pulling, and so that I'll have a merge > message explaining things for later. > > I've done this myself this time, but please make your pull requests > legible in the future. The patch series you merged even had a cover > letter, please keep track of these things and don't make people search > for them. > > Linus I'll keep this is mind and yeah, get the frustration with this. BR, Jarkko ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] KEYS: for-next-keys-7.2-rc6 2026-07-28 0:49 ` Jarkko Sakkinen @ 2026-07-28 0:50 ` Jarkko Sakkinen 0 siblings, 0 replies; 5+ messages in thread From: Jarkko Sakkinen @ 2026-07-28 0:50 UTC (permalink / raw) To: Linus Torvalds Cc: David Howells, Herbert Xu, David S. Miller, keyrings, linux-integrity, Fabrice Derepas, Michael Bommarito On Tue, Jul 28, 2026 at 03:49:28AM +0300, Jarkko Sakkinen wrote: > On Mon, Jul 27, 2026 at 02:22:47PM -0700, Linus Torvalds wrote: > > On Mon, 27 Jul 2026 at 11:46, Jarkko Sakkinen <jarkko@kernel.org> wrote: > > > > > > This pull request contains bug fixes discussed in [1] and two fixes > > > (in one commit) from Fabrice for DCP trusted keys backend.. > > > > Please don't explain commits with links. The commit log is supposed to > > be legible without a network connection. Links are ok as supplements > > and background information, but not as a "this is explained by link". > > > > And the pull request is supposed to have what I can useas that commit > > log (either in the email or in the tag). Yes, I edit things for > > clarity and consistency, but I don't want to follow links and try to > > figure out what some discussion was all about. > > > > So please give me an explanation for what you are asking me to pull. > > Both so that I see what I'm pulling, and so that I'll have a merge > > message explaining things for later. > > > > I've done this myself this time, but please make your pull requests > > legible in the future. The patch series you merged even had a cover > > letter, please keep track of these things and don't make people search > > for them. > > > > Linus > > I'll keep this is mind and yeah, get the frustration with this. Right, and thanks for still merging it. BR, Jarkko ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] KEYS: for-next-keys-7.2-rc6 2026-07-27 18:45 [GIT PULL] KEYS: for-next-keys-7.2-rc6 Jarkko Sakkinen 2026-07-27 21:22 ` Linus Torvalds @ 2026-07-27 21:50 ` pr-tracker-bot 1 sibling, 0 replies; 5+ messages in thread From: pr-tracker-bot @ 2026-07-27 21:50 UTC (permalink / raw) To: Jarkko Sakkinen Cc: Linus Torvalds, David Howells, Herbert Xu, David S. Miller, keyrings, linux-integrity, Fabrice Derepas, Michael Bommarito The pull request you sent on Mon, 27 Jul 2026 21:45:58 +0300: > git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/for-next-keys-7.2-rc6 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/aa6fc3defb36b11eb82c4d1f4e95b5f6d8a0bca6 Thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/prtracker.html ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-07-28 0:50 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2026-07-27 18:45 [GIT PULL] KEYS: for-next-keys-7.2-rc6 Jarkko Sakkinen 2026-07-27 21:22 ` Linus Torvalds 2026-07-28 0:49 ` Jarkko Sakkinen 2026-07-28 0:50 ` Jarkko Sakkinen 2026-07-27 21:50 ` pr-tracker-bot
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.