From: Steven Rostedt <rostedt@goodmis.org>
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] trace_irqsoff: remove redundant reset per-CPU buff
Date: Fri, 5 Feb 2016 10:04:26 -0500 [thread overview]
Message-ID: <20160205100426.72fa51b2@gandalf.local.home> (raw)
In-Reply-To: <CAJwJo6a+sgGRCaPQMyYy7o2QtS3BhuAuT=ZbBYYLx77WkbY2Pw@mail.gmail.com>
On Fri, 5 Feb 2016 14:52:53 +0300
Dmitry Safonov <0x7f454c46@gmail.com> wrote:
> Thanks, Steve!
> Yeah, I know it may take time to get to unimportant patches
> that are also mostly cleanups.
>
Also, FYI, even if you do an RFC, include "PATCH" in the brackets as
well. I usually have "[RFC][PATCH]". Because when I'm looking for
patches in my inbox, I will filter for PATCH. If a patch is out there
without that in the subject, it is much more likely to be missed (and
most likely will).
-- Steve
next prev parent reply other threads:[~2016-02-05 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 18:10 [RFC] trace_irqsoff: remove redundant reset per-CPU buff Dmitry Safonov
2015-11-03 18:25 ` Dmitry Safonov
2015-11-03 18:37 ` Steven Rostedt
2016-02-05 2:40 ` Steven Rostedt
2016-02-05 11:52 ` Dmitry Safonov
2016-02-05 14:40 ` Steven Rostedt
2016-02-05 15:04 ` Steven Rostedt [this message]
2016-02-05 15:56 ` Dmitry Safonov
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=20160205100426.72fa51b2@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=0x7f454c46@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).