[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180412142845.6b97b223@gandalf.local.home>
Date: Thu, 12 Apr 2018 14:28:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Konstantin Ryabitsev <mricon@...nel.org>
Subject: Re: [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and
fixes
On Thu, 12 Apr 2018 10:58:21 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Thu, Apr 12, 2018 at 10:53 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > That doesn't exist, and makes no sense. Did you mean tracing, not ktest?
>
> Oh, it's more f'ed up than that. That "ktest-v4.17-2" tag does exist -
> in the tracing tree.
>
> So the tag is mis-named, but in the right tree, and then your pull
> request points at the wrong tree.
>
> Do you want to fix that all up, or should I just pull from that messed-up thing?
>
Grumble, no don't pull it. Let me fix it.
That's what I get when I up-arrow commands. I'll retag it and make sure
it's fine, and send you another pull request.
Oh, and I just received my nitrokey and I'm playing with it. One thing
I found is that it doesn't like keys sized 3072 (gives me a bad key
error), which is my current subkey. So I created a new subkey:
Primary key fingerprint: 5ED9 A48F C54C 0A22 D1D0 804C EBC2 6CDB 5A56 DE73
Subkey fingerprint: B5D7 BDD5 67E0 67A3 EE0C 9FBE 3F0B D661 FC59 E3D3
That is 4096. I pushed it to the key servers about a half hour ago,
hopefully, it has made its way around, as I'm going to start using it.
-- Steve
Powered by blists - more mailing lists