From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: trivial@rustcorp.com.au, Dipankar Sarma <dipankar@in.ibm.com>,
"open list:READ-COPY UPDATE..." <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] update reference, kerneltrap.org no longer works
Date: Mon, 9 Jun 2014 09:08:16 -0700 [thread overview]
Message-ID: <20140609160816.GC4581@linux.vnet.ibm.com> (raw)
In-Reply-To: <1402329088-4802-1-git-send-email-bobby.prani@gmail.com>
On Mon, Jun 09, 2014 at 11:51:23AM -0400, Pranith Kumar wrote:
> kerneltrap.org no longer works, update to a working reference
>
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
Queued for 3.17, thank you!
FYI, I updated the commit message to read as follows:
------------------------------------------------------------------------
documentation: Update reference, kerneltrap.org no longer works
The kerneltrap.org site no longer works, so this commit updates it to
a working reference, namely gmane.
Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
------------------------------------------------------------------------
I added the "documentation:" tag (as opposed to "rcu:" for core RCU code
or "rcutorture:" for RCU stress-test code) and capitalized the first word
of the subject line, and made a complete sentence out of the commit log.
No worries if you would rather not do this, but just FYI.
Thanx, Paul
> ---
> Documentation/RCU/RTFP.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/RCU/RTFP.txt b/Documentation/RCU/RTFP.txt
> index 2f0fcb2..f29bcbc 100644
> --- a/Documentation/RCU/RTFP.txt
> +++ b/Documentation/RCU/RTFP.txt
> @@ -2451,8 +2451,8 @@ lot of {Linux} into your technology!!!"
> ,month="February"
> ,year="2010"
> ,note="Available:
> -\url{http://kerneltrap.com/mailarchive/linux-netdev/2010/2/26/6270589}
> -[Viewed March 20, 2011]"
> +\url{http://thread.gmane.org/gmane.linux.network/153338}
> +[Viewed June 9, 2014]"
> ,annotation={
> Use a pair of list_head structures to support RCU-protected
> resizable hash tables.
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-06-09 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 15:51 [PATCH 1/6] update reference, kerneltrap.org no longer works Pranith Kumar
2014-06-09 15:51 ` [PATCH 2/6] remove dead link, " Pranith Kumar
2014-06-09 15:51 ` [PATCH 3/6] update reference, " Pranith Kumar
2014-06-09 15:51 ` [PATCH 4/6] " Pranith Kumar
2014-06-09 15:51 ` [PATCH 5/6] " Pranith Kumar
2014-06-09 15:51 ` [PATCH 6/6] remove dead link, " Pranith Kumar
2014-06-09 16:08 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-09 15:55 [PATCH 1/6] update reference, " Pranith Kumar
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=20140609160816.GC4581@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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