[PATCH] documentation: fix broken lkml archive links in RCU requirements

From: Michael Opdenacker
Date: Fri Sep 09 2016 - 09:43:35 EST

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:

Signed-off-by: Michael Opdenacker <michael.opdenacker@xxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxxxx";>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 &ldquo;eventually&rdquo; being controlled by the
@@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option.
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@xxxxxxxxxxxxxx";>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@xxxxxxxxxxxxxx";>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@xxxxxxxxxxxxxx";>an algorithm</a>