| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <D2EDFCP44XUT.3S3KNTQK1W4XG@iki.fi> Date: Mon, 01 Jul 2024 17:16:23 +0000 From: "Jarkko Sakkinen" <jarkko.sakkinen@....fi> To: "Linus Torvalds" <torvalds@...ux-foundation.org>, "Jarkko Sakkinen" <jarkko@...nel.org> Cc: "Peter Huewe" <peterhuewe@....de>, "Jason Gunthorpe" <jgg@...pe.ca>, "David Howells" <dhowells@...hat.com>, <keyrings@...r.kernel.org>, <linux-integrity@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.11-rc1 On Mon Jul 1, 2024 at 4:35 PM UTC, Linus Torvalds wrote: > On Mon, 1 Jul 2024 at 08:51, Jarkko Sakkinen <jarkko@...nel.org> wrote: > > > > Contains couple of bug fixes. > > This - and your keys pull - say 6.11-rc1 (and say "next"), but don't > really look like the usual merge window stuff. No new features are coming for this release. I had one in progress but decided to let it mature up until 6.12 [1]. I have one known bug fix upcoming [2], which I'll send after I've received feedback from Stefan Berger [3]. The second reason for postponing features is that deploying encrypted bus is a substantial infrastructural change so it is better to have bandwidth to fix any possible issues when it ends up to production kernels. So yeah, not a usual pull request, but it is still planned unusual one... > > Just checking. > > Linus [1] https://lore.kernel.org/linux-integrity/20240528210823.28798-1-jarkko@kernel.org/T/#t [2] https://lore.kernel.org/linux-integrity/20240701170735.109583-1-jarkko@kernel.org/T/#u [3] https://lore.kernel.org/linux-integrity/9f86a167074d9b522311715c567f1c19b88e3ad4.camel@kernel.org/ BR, Jarkko
Powered by blists - more mailing lists