From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: paulmck@linux.vnet.ibm.com, corbet@lwn.net
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: [PATCH] documentation: fix broken lkml archive links in RCU requirements
Date: Fri, 9 Sep 2016 15:43:06 +0200 [thread overview]
Message-ID: <1473428586-16491-1-git-send-email-michael.opdenacker@free-electrons.com> (raw)
Fix 4 LKML archive links that became broken (data loss
on mail-archive.com?)
Working links were found on Paul McKenney's RCU articles
on LWN.net, from which the documentation originates:
http://lwn.net/Articles/652156/
http://lwn.net/Articles/652677/
http://lwn.net/Articles/653326/
Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
---
Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html
index ece410f40436..2adb3d43ce44 100644
--- a/Documentation/RCU/Design/Requirements/Requirements.html
+++ b/Documentation/RCU/Design/Requirements/Requirements.html
@@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's
<a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a>
efforts, memory footprint is critically important on single-CPU systems with
non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus
-<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a>
+<a href="http://lkml.org/lkml/2009/1/14/449">tiny RCU</a>
was born.
Josh Triplett has since taken over the small-memory banner with his
<a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a>
@@ -1975,7 +1975,7 @@ guard against mishaps and misuse:
and cleaned up with <tt>destroy_rcu_head()</tt>.
Mathieu Desnoyers made me aware of this requirement, and also
supplied the needed
- <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>.
+ <a href="https://lkml.org/lkml/2010/3/18/417">patch</a>.
<li> An infinite loop in an RCU read-side critical section will
eventually trigger an RCU CPU stall warning splat, with
the duration of “eventually” being controlled by the
@@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option.
<p>
This all should be quite obvious, but the fact remains that
Linus Torvalds recently had to
-<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a>
+<a href="https://lkml.org/lkml/2015/4/14/616">remind</a>
me of this requirement.
<h3><a name="Firmware Interface">Firmware Interface</a></h3>
@@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including
The name notwithstanding, some Linux-kernel architectures
can have nested NMIs, which RCU must handle correctly.
Andy Lutomirski
-<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a>
+<a href="https://lkml.org/lkml/2014/11/21/642">surprised me</a>
with this requirement;
he also kindly surprised me with
<a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a>
--
2.7.4
next reply other threads:[~2016-09-09 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:43 Michael Opdenacker [this message]
2016-09-09 14:17 ` [PATCH] documentation: fix broken lkml archive links in RCU requirements Richard Weinberger
2016-09-09 14:33 ` Paul E. McKenney
2016-09-15 12:00 ` Michael Opdenacker
2016-09-09 14:34 ` Steven Rostedt
2016-09-15 12:06 ` Michael Opdenacker
2016-09-15 12:17 ` Michael Opdenacker
2016-09-15 13:18 ` Steven Rostedt
2016-09-15 14:49 ` 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=1473428586-16491-1-git-send-email-michael.opdenacker@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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).