From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20
Date: Fri, 30 Nov 2018 09:41:00 -0800 [thread overview]
Message-ID: <CAHk-=wgVQNNB6XhJQMwyQdc1B5Qh3nMXhixK5uzbdeOOnwOmdw@mail.gmail.com> (raw)
In-Reply-To: <20181130031829.268422593@goodmis.org>
On Thu, Nov 29, 2018 at 7:19 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Note, this is on top of a previous git pull that I have submitted:
>
> http://lkml.kernel.org/r/20181127224031.76681fe0@vmware.local.home
Hmm.
I had dismissed that, because the patch descriptors for that series
had had "for-next" in them.
https://lore.kernel.org/lkml/20181122002801.501220343@goodmis.org/
so I dismissed that pull request entirely as being not for this
release entirely.
I went back and merged things, but in general, please try to avoid
confusing me. I'm easily confused when I get mixed messages about the
patches and the pull requests, and will then generally default to
"ignore, this is informational".
Linus
next prev parent reply other threads:[~2018-11-30 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:18 [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20 Steven Rostedt
2018-11-30 3:18 ` [PATCH 1/2] tracepoint: Use __idx instead of idx in DO_TRACE macro to make it unique Steven Rostedt
2018-11-30 3:18 ` [PATCH 2/2] tracing/fgraph: Fix set_graph_function from showing interrupts Steven Rostedt
2018-11-30 17:41 ` Linus Torvalds [this message]
2018-11-30 18:13 ` [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20 Steven Rostedt
2018-11-30 18:56 ` Linus Torvalds
2018-11-30 19:35 ` Steven Rostedt
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='CAHk-=wgVQNNB6XhJQMwyQdc1B5Qh3nMXhixK5uzbdeOOnwOmdw@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).