linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes
Date: Thu, 12 Apr 2018 10:53:41 -0700	[thread overview]
Message-ID: <CA+55aFxHPAzO-U+Q2RVjpAd4T6oM_Puor5qRC8pPYOdohO2L_w@mail.gmail.com> (raw)
In-Reply-To: <20180412015359.244491749@goodmis.org>

On Wed, Apr 11, 2018 at 6:53 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Please pull the latest ktest-v4.17-2 tree, which can be found at:

That doesn't exist, and makes no sense. Did you mean tracing, not ktest?

And even if you did, why did your scripts not notice that the branch
you point to doesn't actually exist?

               Linus

  parent reply	other threads:[~2018-04-12 17:53 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 ` Linus Torvalds [this message]
2018-04-12 17:58   ` [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes Linus Torvalds
2018-04-12 18:28     ` Steven Rostedt
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=CA+55aFxHPAzO-U+Q2RVjpAd4T6oM_Puor5qRC8pPYOdohO2L_w@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.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).