From: "Jarkko Sakkinen" <jarkko.sakkinen@iki.fi>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Jarkko Sakkinen" <jarkko@kernel.org>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"David Howells" <dhowells@redhat.com>, <keyrings@vger.kernel.org>,
<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.11-rc1
Date: Mon, 01 Jul 2024 17:16:23 +0000 [thread overview]
Message-ID: <D2EDFCP44XUT.3S3KNTQK1W4XG@iki.fi> (raw)
In-Reply-To: <CAHk-=wjYe22cLAF=LmZwRu3VOf80LO6XdsdYt3Lhb_TEJ0XnPA@mail.gmail.com>
On Mon Jul 1, 2024 at 4:35 PM UTC, Linus Torvalds wrote:
> On Mon, 1 Jul 2024 at 08:51, Jarkko Sakkinen <jarkko@kernel.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
next prev parent reply other threads:[~2024-07-01 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 15:51 [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.11-rc1 Jarkko Sakkinen
2024-07-01 16:35 ` Linus Torvalds
2024-07-01 17:16 ` Jarkko Sakkinen [this message]
2024-07-16 0:03 ` 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=D2EDFCP44XUT.3S3KNTQK1W4XG@iki.fi \
--to=jarkko.sakkinen@iki.fi \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--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