All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Michael Opdenacker <michael.opdenacker@free-electrons.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Josh Triplett <josh@joshtriplett.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements
Date: Fri, 9 Sep 2016 07:33:55 -0700	[thread overview]
Message-ID: <20160909143355.GJ32751@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFLxGvzJYy=cTKc=NPpw8mUs68ZQck85R7jCK2hT6qszfBn_Cg@mail.gmail.com>

On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote:
> Michael,
> 
> On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker
> <michael.opdenacker@free-electrons.com> wrote:
> > 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>.
> 
> Please don't add lkml.org. It does not use message ids for indexing.
> With knowing the message id you can query any other archive.
> e.g. http://marc.info/?i=20100319013024.GA28456@Krystal
> By adding lkml.org you kill that information. Archives come and go,
> the message id is the only common query id we have.
> 
> IMHO kernel.org admins should fix/improve their redirection service to
> point to a working service.

There has been some instability in the kernel.org redirection.  Right
now, the /r/ services seems to work, though as noted the /g/ does not.
Please report this to the Kernel.org administrators:

	https://kernel.org/category/contact-us.html

							Thanx, Paul

  reply	other threads:[~2016-09-09 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 13:43 [PATCH] documentation: fix broken lkml archive links in RCU requirements Michael Opdenacker
2016-09-09 14:17 ` Richard Weinberger
2016-09-09 14:33   ` Paul E. McKenney [this message]
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=20160909143355.GJ32751@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=richard.weinberger@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.