From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Konstantin Ryabitsev <mricon@kernel.org>
Subject: Re: [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes
Date: Thu, 12 Apr 2018 14:28:45 -0400 [thread overview]
Message-ID: <20180412142845.6b97b223@gandalf.local.home> (raw)
In-Reply-To: <CA+55aFzPhRdZSX2wMiiact8RpnYMHy48RK+Ng7n_Ek_vpYy3fg@mail.gmail.com>
On Thu, 12 Apr 2018 10:58:21 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Apr 12, 2018 at 10:53 AM, Linus Torvalds
> <torvalds@linux-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
next prev parent reply other threads:[~2018-04-12 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 1:53 [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes Steven Rostedt
2018-04-12 1:54 ` [PATCH 2/5] tracing/uprobe: Add support for overlayfs Steven Rostedt
2018-04-12 1:54 ` [PATCH 3/5] trace_uprobe: Use %lx to display offset Steven Rostedt
2018-04-12 1:54 ` [PATCH 4/5] trace_uprobe: Simplify probes_seq_show() Steven Rostedt
2018-04-12 1:54 ` [PATCH 5/5] tracing: Enforce passing in filter=NULL to create_filter() Steven Rostedt
2018-04-12 17:53 ` [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes Linus Torvalds
2018-04-12 17:58 ` Linus Torvalds
2018-04-12 18:28 ` Steven Rostedt [this message]
2018-04-12 19:00 ` Konstantin Ryabitsev
2018-04-12 19:46 ` Steven Rostedt
2018-04-12 19:55 ` Konstantin Ryabitsev
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=20180412142845.6b97b223@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mricon@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).