LKML Archive on lore.kernel.org
 help / color / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Opdenacker <michael.opdenacker@free-electrons.com>,
	corbet@lwn.net, josh@joshtriplett.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements
Date: Thu, 15 Sep 2016 07:49:26 -0700
Message-ID: <20160915144926.GD10850@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160915091828.4ae347e9@gandalf.local.home>

On Thu, Sep 15, 2016 at 09:18:28AM -0400, Steven Rostedt wrote:
> On Thu, 15 Sep 2016 14:17:06 +0200
> Michael Opdenacker <michael.opdenacker@free-electrons.com> wrote:
> 
> > Fix 4 LKML archive links that became broken
> > (issue with https://lkml.kernel.org/g/ redirection links)
> > 
> > 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..1c39a2362911 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="https://lkml.kernel.org/r/20090113221724.GA15307@linux.vnet.ibm.com">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.kernel.org/r/20100319013024.GA28456@Krystal">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.
> >  <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.kernel.org/r/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">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.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">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>
> 
> Strange that this one still works. Anyway...
> 
> 
> Acked-by: Steven Rostedt <rostedt@goodmis.org>

So we are confident that these links won't be fixed by the next merge
window?

							Thanx, Paul

      reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 13:43 Michael Opdenacker
2016-09-09 14:17 ` 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 [this message]

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=20160915144926.GD10850@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.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=michael.opdenacker@free-electrons.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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
	git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git