From: Vineet Gupta <vineet.gupta@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Vineet Gupta <vgupta@kernel.org>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Yu-Chun Lin <eleanor15x@gmail.com>,
Thomas Huth <thuth@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [GIT PULL] ARC updates for 6.16
Date: Thu, 12 Jun 2025 09:12:09 -0700 [thread overview]
Message-ID: <755cf90e-acf5-46d1-9ac4-2ea06c93e873@linux.dev> (raw)
In-Reply-To: <CAHk-=wgda=j0VNdx1gTos_4DL986Z2cKotgpVsn36T-JmNshXg@mail.gmail.com>
On 6/12/25 08:26, Linus Torvalds wrote:
> On Wed, 11 Jun 2025 at 20:29, Vineet Gupta <vgupta@kernel.org> wrote:
>> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/ tags/arc-6.16-rc1
> So this is signed and I pulled, but your key has expired. And I don't
> find a new key on kernel.org or the normal keyservers.
>
> Please don't put expiration dates on your keys and then not refresh
> them. Or tell me where to find updated key/.
Sorry about this and thx for pulling anyways.
Back when ii had happened I did extend the date on the key and AFAIKR did
--send-keys to pgp.mit.edu
I've redone this and today also sent it over for inclusion into kernel.org pgp repo.
pub rsa4096 2013-02-16 [SC] [expires: 2029-12-08]
397A6E0AE47A85E76B74B08969D7F1DDE28AC25E
uid [ unknown] Vineet Gupta (kernel) <vgupta@kernel.org>
uid [ unknown] Vineet Gupta (linux) <vineet.gupta@linux.dev>
uid [ unknown] Vineet Gupta (personal) <vineetg76@gmail.com>
uid [ unknown] Vineet Gupta (alias) <vgupta@synopsys.com>
uid [ unknown] Vineet Gupta (official) <vineet.gupta1@synopsys.com>
uid [ unknown] [jpeg image of size 24452]
Thx,
-Vineet
next prev parent reply other threads:[~2025-06-12 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 3:29 Vineet Gupta
2025-06-12 15:26 ` Linus Torvalds
2025-06-12 16:12 ` Vineet Gupta [this message]
2025-06-12 16:58 ` Linus Torvalds
2025-06-12 15:29 ` 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=755cf90e-acf5-46d1-9ac4-2ea06c93e873@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=eleanor15x@gmail.com \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=thuth@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@kernel.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
all inboxes | Powered by JetHome®