From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Prateek Sood <prsood@codeaurora.org>
Subject: Re: [GIT PULL v2] tracing: A couple of minor fixes
Date: Mon, 21 Oct 2019 16:34:36 -0400 [thread overview]
Message-ID: <20191021163436.13acca67@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=whCRAsQTKkR88bUgZ-6ET45U++47V=8L_H9YGCk7n-U7w@mail.gmail.com>
On Mon, 21 Oct 2019 16:30:14 -0400
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Oct 21, 2019 at 3:19 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Two minor fixes:
> >
> > - A race in perf trace initialization (missing mutexes)
>
> Are you sure you fixed the crud?
>
> That commit still has a very odd commit message with an oops and
> ramdump at the top, before the explanation.
>
I can clean it up some more. I just deleted from the original:
"Could you please confirm:
1) the race mentioned below exists or not.
2) if following patch fixes it.
>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8>8 "
That was in it.
These are minor fixes, so there's no rush. I'll look at it tonight and
see if I can make the change log a little nicer.
-- Steve
prev parent reply other threads:[~2019-10-21 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 16:45 [GIT PULL] " Steven Rostedt
2019-10-21 19:13 ` Steven Rostedt
2019-10-21 19:19 ` [GIT PULL v2] " Steven Rostedt
2019-10-21 20:30 ` Linus Torvalds
2019-10-21 20:34 ` Steven Rostedt [this message]
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=20191021163436.13acca67@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prsood@codeaurora.org \
--cc=torvalds@linux-foundation.org \
--cc=zhengjun.xing@linux.intel.com \
/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
all inboxes | Powered by JetHome®