All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikil Paul S <snikilpaul@gmail.com>
To: corbet@lwn.net
Cc: skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, snikilpaul@gmail.com
Subject: [PATCH 2/2] docs: rcu: Update dead OLS link in RTFP.txt
Date: Mon, 11 Aug 2025 12:38:37 +0000	[thread overview]
Message-ID: <20250811123837.4378-3-snikilpaul@gmail.com> (raw)
In-Reply-To: <20250811123837.4378-1-snikilpaul@gmail.com>

From: Nikil <snikilpaul@gmail.com>

Replace a dead link to the OLS 2001 Proceedings with a working
version hosted on kernel.org.
Signed-off-by: Nikil Paul S <snikilpaul@gmail.com>
---
 Documentation/RCU/RTFP.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/RCU/RTFP.txt b/Documentation/RCU/RTFP.txt
index db8f16b392aa..87b1c97c3ec3 100644
--- a/Documentation/RCU/RTFP.txt
+++ b/Documentation/RCU/RTFP.txt
@@ -641,7 +641,7 @@ Orran Krieger and Rusty Russell and Dipankar Sarma and Maneesh Soni"
 ,Month="July"
 ,Year="2001"
 ,note="Available:
-\url{http://www.linuxsymposium.org/2001/abstracts/readcopy.php}
+\url{https://www.kernel.org/doc/ols/2001/read-copy.pdf}
 \url{http://www.rdrop.com/users/paulmck/RCU/rclock_OLS.2001.05.01c.pdf}
 [Viewed June 23, 2004]"
 ,annotation={
-- 
2.43.0


  parent reply	other threads:[~2025-08-11 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 12:38 [PATCH v2 0/2] docs: fix dead OLS links in timers and RCU docs Nikil Paul S
2025-08-11 12:38 ` [PATCH 1/2] docs: timers: Update dead OLS link in timekeeping docs Nikil Paul S
2025-08-11 12:38 ` Nikil Paul S [this message]
2025-08-12  6:38   ` [PATCH 2/2] docs: rcu: Update dead OLS link in RTFP.txt Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2025-08-12  9:48 Nikil Paul S
2025-08-12 12:02 ` Matthew Wilcox

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=20250811123837.4378-3-snikilpaul@gmail.com \
    --to=snikilpaul@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=skhan@linuxfoundation.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.