From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper
Date: Tue, 7 Jan 2020 13:58:24 +0100 [thread overview]
Message-ID: <20200107125824.GA2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191223022532.14864-1-longman@redhat.com>
On Sun, Dec 22, 2019 at 09:25:32PM -0500, Waiman Long wrote:
> It turns out that the URL of the MCS lock paper listed in the source
> code is no longer accessible. I did got question about where the paper
> was. This patch updates the URL to one that is still accessible.
>
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
> kernel/locking/qspinlock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index 2473f10c6956..1d008d2333c0 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -34,7 +34,7 @@
> * MCS lock. The paper below provides a good description for this kind
> * of lock.
> *
> - * http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
> + * https://www.cs.rochester.edu/u/scott/papers/1991_TOCS_synch.pdf
Do we want to stick a copy of the paper in our bugzilla and link that
instead? ISTR we do something similar elsewhere, but I'm having trouble
finding it.
Thomas, Konstantin?
next prev parent reply other threads:[~2020-01-07 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 2:25 [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper Waiman Long
2020-01-07 12:58 ` Peter Zijlstra [this message]
2020-01-07 13:09 ` Peter Zijlstra
2020-01-07 14:14 ` Waiman Long
2020-01-07 17:23 ` Will Deacon
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=20200107125824.GA2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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