From: Yury Norov <yury.norov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Luo Jie <quic_luoj@quicinc.com>, Andrea Righi <arighi@nvidia.com>
Subject: Re: [GIT PULL] bitmap fixes for 6.16
Date: Thu, 29 May 2025 18:43:11 -0400 [thread overview]
Message-ID: <aDji_0NEVRpIZMKP@yury> (raw)
In-Reply-To: <CAHk-=whi6O47-0r=eOJHnd1ACa83Kd-aaELi=Tw4p4HwJ74q2w@mail.gmail.com>
On Wed, May 28, 2025 at 02:42:36PM -0700, Linus Torvalds wrote:
> On Tue, 27 May 2025 at 12:03, Yury Norov <yury.norov@gmail.com> wrote:
> >
> > Please notice I changed my pgp key.
>
> Well, I'm not finding your new key anywhere, so I can't even check
> that the new key is signed with the old one.
>
> So I can't pull this.
I have to admit I'm not an expert in pgp keys things. So when my upstream
laptop bricked, I switched to a spare one and just generated a new key.
This is obviously a wrong way to go.
Today I bought an ssd-usb adapter, plugged my old ssd, and it is
fortunately alive. I was able to copy the old key on my new machine,
and it seemingly works.
If no objections, I think the simplest way is to resend this request
with the key you're familiar to.
Sorry for inconvenience.
Thanks,
Yury
next prev parent reply other threads:[~2025-05-29 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 19:03 [GIT PULL] bitmap fixes for 6.16 Yury Norov
2025-05-28 21:42 ` Linus Torvalds
2025-05-29 22:43 ` Yury Norov [this message]
2025-05-30 3:59 ` Linus Torvalds
2025-06-03 16:09 ` 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=aDji_0NEVRpIZMKP@yury \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arighi@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=quic_luoj@quicinc.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