public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: christophe.leroy@csgroup.eu, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, nysal@linux.ibm.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.11-3 tag
Date: Sat, 07 Sep 2024 09:11:30 +1000	[thread overview]
Message-ID: <87o7504btp.fsf@mail.lhotse> (raw)
In-Reply-To: <CAHk-=wj6L6Qb10jVk+eHH2D3oHFathTc2nnZRpKKbqKuO3Rkow@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, 6 Sept 2024 at 05:08, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Please pull some more powerpc fixes for 6.11:
>>
>>   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.11-3
>
> Hmm. New pgp key? Please don't take me by surprise like this.

Yes, sorry. I switched to it a few weeks back but this is the first pull
request I've sent since.

> The key looks fine, I see the signature by Stephen Rothwell, but I get
> worried when I suddenly see a new signature with no notice and then
> have to go looking around for it.

It's also signed by my old key.

I posted it to the keys repo:
  https://lore.kernel.org/keys/87o75pp2bt.fsf@mail.lhotse/

But yeah I still should have mentioned it in the pull request.

cheers

  reply	other threads:[~2024-09-06 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 12:07 [GIT PULL] Please pull powerpc/linux.git powerpc-6.11-3 tag Michael Ellerman
2024-09-06 19:57 ` Linus Torvalds
2024-09-06 23:11   ` Michael Ellerman [this message]
2024-09-06 20:28 ` 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=87o7504btp.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nysal@linux.ibm.com \
    --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