[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130820042832.GZ29406@linux.vnet.ibm.com>
Date: Mon, 19 Aug 2013 21:28:32 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...icios.com, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com,
edumazet@...gle.com, darren@...art.com, fweisbec@...il.com,
sbw@....edu
Subject: Re: [PATCH tip/core/rcu 0/3] v2 Documentation updates for 3.12
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.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists