From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
LKML <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements
Date: Thu, 15 Sep 2016 14:06:33 +0200 [thread overview]
Message-ID: <f3a76e2a-5846-b555-8e54-a95b6d75534d@free-electrons.com> (raw)
In-Reply-To: <20160909103402.09216e43@gandalf.local.home>
Hi Steve,
On 09/09/2016 16:34, Steven Rostedt wrote:
> Correct, we avoid any links to lkml.org at all costs. Simple do a
>
> s,/g/,/r/, and all your links should work. For example, using the above
> mentioned link:
>
> https://lkml.kernel.org/r/20100319013024.GA28456@Krystal
>
> Works as expected.
I confirm that all the links work indeed. I'm sending a patch update
right away.
Thanks!
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-15 12:06 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
2016-09-15 12:00 ` Michael Opdenacker
2016-09-09 14:34 ` Steven Rostedt
2016-09-15 12:06 ` Michael Opdenacker [this message]
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=f3a76e2a-5846-b555-8e54-a95b6d75534d@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=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 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).