linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Cgroups <cgroups@vger.kernel.org>
Subject: Re: [GIT PULL] cgroup changes for v5.19-rc1
Date: Wed, 25 May 2022 09:56:15 -1000	[thread overview]
Message-ID: <Yo6J3/cVHu4huZH1@slm.duckdns.org> (raw)
In-Reply-To: <CAHk-=wj4Q2++KfQ4NhMtjmJF_1bjC-573U61o1acuHfqmsvCKA@mail.gmail.com>

On Wed, May 25, 2022 at 12:47:48PM -0700, Linus Torvalds wrote:
> On Wed, May 25, 2022 at 12:44 PM Tejun Heo <tj@kernel.org> wrote:
> >
> > Hahaha, yeah, I lost my private key many years ago, so gotta get that sorted
> > out first. Will do the signed pull from now on.
> 
> You have a pgp key for your kernel.org account, you can just use that. No?
>
> (That way I'll also be able to just pick it up from the pgp key repo
> that Konstantin maintains).

I don't have the private part of that pgp key anymore and have been just
using the same ssh key. Nothing really requires the private key that I lost
at least 5 years ago. On the plus side, the pgp key has been as secure as it
gets. :) So, I gotta generate new keys, get it signed and replace the korg
key and so on. I've just been really lazy.

Thanks.

-- 
tejun

      reply	other threads:[~2022-05-25 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 23:44 [GIT PULL] cgroup changes for v5.19-rc1 Tejun Heo
2022-05-25 19:40 ` pr-tracker-bot
2022-05-25 19:43 ` Linus Torvalds
2022-05-25 19:44   ` Tejun Heo
2022-05-25 19:47     ` Linus Torvalds
2022-05-25 19:56       ` Tejun Heo [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=Yo6J3/cVHu4huZH1@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).