From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: <dhowells@redhat.com>, "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: Mon, 01 Apr 2024 16:17:50 +0300 [thread overview]
Message-ID: <D08TD4LASWJO.30BX8927MB1YK@kernel.org> (raw)
In-Reply-To: <CAHk-=wi-VWatwU5Gi6n74LF66dRWCo4dUozwj_DwTBRO-wDFcA@mail.gmail.com>
On Sun Mar 31, 2024 at 8:01 PM EEST, Linus Torvalds wrote:
> On Sat, 30 Mar 2024 at 22:57, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > 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.
>
> It's perfectly fine if you send me key updates - you're listed as
> maintainer etc, that's not a problem.
>
> But when I get a tag name that says "tpmdd" and a subject that says
> "tpmdd", I'm noty expecting to then see key updates in the pull.
>
> So that part of my issue was literally just that your subject line and
> tag name didn't match the contents, and that just makes me go "there's
> something wrong here".
>
> So keys coming through your tree is fine per se, it's just that I want
> the subject line etc to actually make sense.
>
> Linus
OK, I'll we'll address no problem :-) I think separate tag and
appropriate subject line is sufficient change as we always sync
up with these (through IRC channel), i.e. David is aware when
I send anything keyring specific.
BR, Jarkko
prev parent reply other threads:[~2024-04-01 13:17 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
2024-03-31 17:01 ` Linus Torvalds
2024-04-01 13:17 ` Jarkko Sakkinen [this message]
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=D08TD4LASWJO.30BX8927MB1YK@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 read-only IMAP folder(s) and NNTP newsgroup(s).