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@polymtl.ca,
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 2/3] rcu: Update RTFP documentation
Date: Mon, 19 Aug 2013 20:22:22 -0700 [thread overview]
Message-ID: <20130820032222.GB4416@leaf> (raw)
In-Reply-To: <1376966267-29949-2-git-send-email-paulmck@linux.vnet.ibm.com>
On Mon, Aug 19, 2013 at 07:37:46PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
>
> Note that this commit also updates the formatting of serveral of the
> bibtex entries to conform to that of my .bib files. I started
> accumulating entries back in the 1980s, back when bibtex insisted
> that comma (",") was a separator, not a terminator. This rule forced
> commas to the fronts of lines. 25 years later, bibtex allows commas
> to be terminators, but I am too lazy to rework all my .bib files.
> Keeping the same format as my .bib files allows my to simply
> incorporate my RCU.bib file into Documentation/RCU/RTFP.txt, which
> is much easier than my earlier practice of keeping track of what
> had changed and adding individual entries. (I sometimes find relevant
> papers that were published some years back, for example.)
>
> In addition, this change adds entries for papers published in the
> last year or so.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
next prev parent reply other threads:[~2013-08-20 3:22 UTC|newest]
Thread overview: 13+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2013-08-18 1:25 [PATCH tip/core/rcu 0/3] " Paul E. McKenney
2013-08-18 1:25 ` [PATCH tip/core/rcu 1/3] rcu: Fix rcu_barrier() documentation Paul E. McKenney
2013-08-18 1:25 ` [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation Paul E. McKenney
2013-08-18 2:46 ` Josh Triplett
2013-08-19 0:20 ` Paul E. McKenney
2013-08-19 0:38 ` Josh Triplett
2013-08-19 4:09 ` Paul E. McKenney
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=20130820032222.GB4416@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@polymtl.ca \
--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).