linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	<dhowells@redhat.com>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<keyrings@vger.kernel.org>
Subject: Re: [GIT PULL] tpmdd changes for v6.9-rc2
Date: Sun, 31 Mar 2024 18:36:45 +0300	[thread overview]
Message-ID: <D081OXSNVFWG.3QW7GEWS2QYAB@kernel.org> (raw)
In-Reply-To: <D07PD5NTOXSQ.30D5V19O6KMQS@kernel.org>

On Sun Mar 31, 2024 at 8:57 AM EEST, Jarkko Sakkinen wrote:
> On Sun Mar 31, 2024 at 12:32 AM EET, Linus Torvalds wrote:
> > On Tue, 26 Mar 2024 at 07:38, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-v6.9-rc2
> >
> > So I haven't pulled this, because the subject line (and tag name)
> > talks about tpmdd, but this is clearly about key handling.
>
> OK, point taken and it is evolutionary issue really but definitely
> needs to be fixed.
>
> I review and test most of the stuff that goes to keyring but other
> than trusted keys, I usually pick only few patches every now and
> then to my tree.
>
> So obviously we need better grounds for putting this content together.
> So probably fastest path to that would be if e.g. David just opens me
> push rights to his tree, and then i push the stuff that makes sense
> to me to some branch in that tree.
>
> In other words: David would take care of sending the final PR.
>
> As per trusted keys, should I start to make a separate "trusted keys
> PR" with its own separate tag? It's fine with me but I just need to
> know how to move forward. E.g. now there is one new hardware backend
> upcoming for trusted keys so now it is good to realig if any need.

Also using separate tag works for me. These changes are synced
in all cases (I sync up with David or vice-versa) so that is
equally good as far as I'm concerned.

BR, Jarkko

  reply	other threads:[~2024-03-31 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 14:38 [GIT PULL] tpmdd changes for v6.9-rc2 Jarkko Sakkinen
2024-03-30 22:32 ` Linus Torvalds
2024-03-31  5:57   ` Jarkko Sakkinen
2024-03-31 15:36     ` Jarkko Sakkinen [this message]
2024-03-31 17:01     ` Linus Torvalds
2024-04-01 13:17       ` Jarkko Sakkinen

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=D081OXSNVFWG.3QW7GEWS2QYAB@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).