From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] tracing: Updates for 5.2
Date: Wed, 15 May 2019 18:21:14 -0700 [thread overview]
Message-ID: <CAHk-=wjfhruWcLo5u=WdP=NKkb_scPamZtfQBgF-UYsF4X41Hw@mail.gmail.com> (raw)
In-Reply-To: <20190515202729.3d62422c@oasis.local.home>
On Wed, May 15, 2019 at 5:27 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> I can do this, but it needs testing and all that before sending to you,
> and may not make the merge window. Is that fine?
It's fine. The warning is annoying, but that's my own fault for
updating my system just before the merge window.
Linus
next prev parent reply other threads:[~2019-05-16 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 17:36 [GIT PULL] tracing: Updates for 5.2 Steven Rostedt
2019-05-15 23:29 ` Linus Torvalds
2019-05-15 23:31 ` Linus Torvalds
2019-05-16 0:27 ` Steven Rostedt
2019-05-16 1:21 ` Linus Torvalds [this message]
2019-05-16 9:08 ` David Laight
2019-05-15 23:50 ` pr-tracker-bot
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-=wjfhruWcLo5u=WdP=NKkb_scPamZtfQBgF-UYsF4X41Hw@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).