From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-doc@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Documentation: RCU: Fix broken link to LKML archive
Date: Sat, 23 Jun 2018 10:06:22 -0700 [thread overview]
Message-ID: <20180623170622.GC3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180623044055.118383-1-joel@joelfernandes.org>
On Fri, Jun 22, 2018 at 09:40:55PM -0700, Joel Fernandes wrote:
> From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
>
> While going through the RCU requirements for interrupts, I noticed that
> one of the LKML links is broken. This patch changes it to use the
> archive from lore.kernel.org which works fine.
>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Good catch, queued for further review, thank you!
Thanx, Paul
> ---
> Documentation/RCU/Design/Requirements/Requirements.html | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html
> index 9b808402f8ce..58b6557007a3 100644
> --- a/Documentation/RCU/Design/Requirements/Requirements.html
> +++ b/Documentation/RCU/Design/Requirements/Requirements.html
> @@ -2269,10 +2269,10 @@ 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>
> +<a href="https://lkml.kernel.org/r/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a>
> that meets this requirement.
>
> <p>
> --
> 2.18.0.rc2.346.g013aa6912e-goog
>
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-doc@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Documentation: RCU: Fix broken link to LKML archive
Date: Sat, 23 Jun 2018 10:06:22 -0700 [thread overview]
Message-ID: <20180623170622.GC3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180623044055.118383-1-joel@joelfernandes.org>
On Fri, Jun 22, 2018 at 09:40:55PM -0700, Joel Fernandes wrote:
> From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
>
> While going through the RCU requirements for interrupts, I noticed that
> one of the LKML links is broken. This patch changes it to use the
> archive from lore.kernel.org which works fine.
>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Good catch, queued for further review, thank you!
Thanx, Paul
> ---
> Documentation/RCU/Design/Requirements/Requirements.html | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html
> index 9b808402f8ce..58b6557007a3 100644
> --- a/Documentation/RCU/Design/Requirements/Requirements.html
> +++ b/Documentation/RCU/Design/Requirements/Requirements.html
> @@ -2269,10 +2269,10 @@ 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>
> +<a href="https://lkml.kernel.org/r/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a>
> that meets this requirement.
>
> <p>
> --
> 2.18.0.rc2.346.g013aa6912e-goog
>
next prev parent reply other threads:[~2018-06-23 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 4:40 [PATCH] Documentation: RCU: Fix broken link to LKML archive Joel Fernandes
2018-06-23 4:40 ` Joel Fernandes
2018-06-23 17:06 ` Paul E. McKenney [this message]
2018-06-23 17:06 ` 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=20180623170622.GC3593@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.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.