linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	darren@dvhart.com, fweisbec@gmail.com, sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 0/3] v2 Documentation updates for 3.12
Date: Mon, 19 Aug 2013 22:05:27 -0700	[thread overview]
Message-ID: <20130820050527.GA7333@leaf> (raw)
In-Reply-To: <20130820042832.GZ29406@linux.vnet.ibm.com>

On Mon, Aug 19, 2013 at 09:28:32PM -0700, Paul E. McKenney wrote:
> On Mon, Aug 19, 2013 at 08:24:11PM -0700, Josh Triplett wrote:
> > On Mon, Aug 19, 2013 at 07:37:17PM -0700, Paul E. McKenney wrote:
> > > Hello!
> > > 
> > > This series provides a few documentation updates:
> > > 
> > > 1.	Update rcu_barrier() documentation to note that it no longer is
> > > 	guaranteed to wait for a full grace period.  This guarantee was
> > > 	a victim of energy efficiency.
> > > 
> > > 2.	Update RTFP documentation.
> > > 
> > > 3.	Fix a control-dependency example in the memory-barriers
> > > 	documentation.
> > > 
> > > Changes from v1 (https://lkml.org/lkml/2013/8/17/94):
> > > 
> > > o	Apply Josh Triplett review comments.
> > 
> > Consider changing the patch tag for new versions, to "PATCH v2" or
> > similar; that way, all of the patches have a clearly distinct subject
> > for the new version.
> > 
> > git format-patch will do this for you; just pass "-v 2".
> 
> Good point, my email client got them confused as well.  My version of git
> format-patch does not know about "-v 2", but --subject-prefix="PATCH v2"
> does fine.  I am using git version 1.8.1.5, for whatever it is worth.

I have 1.8.4.rc3, which has -v.

- Josh Triplett

      reply	other threads:[~2013-08-20  5:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  2:37 [PATCH tip/core/rcu 0/3] v2 Documentation updates for 3.12 Paul E. McKenney
2013-08-20  2:37 ` [PATCH tip/core/rcu 1/3] rcu: Fix rcu_barrier() documentation Paul E. McKenney
2013-08-20  2:37   ` [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation Paul E. McKenney
2013-08-20  3:22     ` Josh Triplett
2013-08-20  2:37   ` [PATCH tip/core/rcu 3/3] doc: Fix memory-barrier control-dependency example Paul E. McKenney
2013-08-20  3:24 ` [PATCH tip/core/rcu 0/3] v2 Documentation updates for 3.12 Josh Triplett
2013-08-20  4:28   ` Paul E. McKenney
2013-08-20  5:05     ` Josh Triplett [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=20130820050527.GA7333@leaf \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=darren@dvhart.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sbw@mit.edu \
    --cc=tglx@linutronix.de \
    /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).