From: Darren Hart <dvhart@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy@infradead.org>
Subject: Re: [GIT PULL] platform-drivers-x86 for 5.1-1
Date: Sun, 10 Mar 2019 15:33:34 -0700 [thread overview]
Message-ID: <20190310223334.GA22126@wrath> (raw)
In-Reply-To: <CAHk-=whvQKUtE1fzTPMwSjNR3nLQBw_DVRVvZEqW5tdTvG63HQ@mail.gmail.com>
On Sun, Mar 10, 2019 at 01:22:24PM -0700, Linus Torvalds wrote:
> On Fri, Mar 8, 2019 at 12:33 PM Darren Hart <dvhart@infradead.org> wrote:
> >
> > The wmi mod alias changes collide with a similar series for TEE based devices.
>
> Anyway, you also used a *very* new subkey. Can you please mention it,
> so that I don't then get taken by surprise when I find a key that was
> used to sign this and I don't have it?
>
> Yes, yes, I will download it anyway, but basically I want the pull
> request to give me enough information that when I do the pull I'm not
> surprised by the result.
>
> That's why the shortlog and diffstat exists of course, but that "don't
> surprise Linus" also covers things like "oh, and the tag will be
> signed with a key you've never seen before".
Will do. Apologies. I almost sent you a note - but didn't after
verifying with others that git-verify-tag still reported "Good
Signature" as the subkey is automatically associated with the master
key - but, point taken - don't surprise Linus. Will err on the side of
more explanation in the future.
Thanks,
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2019-03-10 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 20:33 [GIT PULL] platform-drivers-x86 for 5.1-1 Darren Hart
2019-03-10 20:22 ` Linus Torvalds
2019-03-10 22:33 ` Darren Hart [this message]
2019-03-10 22:30 ` 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=20190310223334.GA22126@wrath \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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