From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chuck Ebbert <cebbert.lkml@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] ring-buffer: Fix infinite spin in reading buffer
Date: Tue, 7 Oct 2014 21:46:36 -0700 [thread overview]
Message-ID: <20141008044636.GB26820@kroah.com> (raw)
In-Reply-To: <20141007214011.158a7b2e@as>
On Tue, Oct 07, 2014 at 09:40:11PM -0500, Chuck Ebbert wrote:
> On Sun, 5 Oct 2014 16:49:43 -0700
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > On Fri, Oct 03, 2014 at 04:20:43PM -0400, Steven Rostedt wrote:
>
> ...
>
> > > Fixes: 651e22f2701b "ring-buffer: Always reset iterator to reader page"
> > > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> >
> > Next time, please also add a Cc: stable... here so that my tools pick
> > it up automatically.
> >
>
> Can you add "Fixes:" to the list of keywords your tools pick up, and
> determine if the patch is needed in -stable by looking at the commit ID
> that's being fixed? Some authors might not remember if the thing being
> fixed has made it into an older release via -stable.
I do that as well, but I don't advertise it as much, as it's easier for
me with the cc: stable marking :)
thanks,
greg k-h
prev parent reply other threads:[~2014-10-08 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 20:20 [GIT PULL] ring-buffer: Fix infinite spin in reading buffer Steven Rostedt
2014-10-05 23:49 ` Greg Kroah-Hartman
2014-10-08 2:23 ` Steven Rostedt
2014-10-08 2:40 ` Chuck Ebbert
2014-10-08 4:46 ` Greg Kroah-Hartman [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=20141008044636.GB26820@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=cebbert.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).