From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org
Cc: corbet@lwn.net, madhuparnabhowmik04@gmail.com,
rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: [PATCH v3 6/7] doc/RCU/rcu: Use https instead of http if possible
Date: Mon, 6 Jan 2020 21:08:01 +0100 [thread overview]
Message-ID: <20200106200802.26994-7-sj38.park@gmail.com> (raw)
In-Reply-To: <20200106200802.26994-1-sj38.park@gmail.com>
From: SeongJae Park <sjpark@amazon.de>
Signed-off-by: SeongJae Park <sjpark@amazon.de>
---
Documentation/RCU/rcu.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RCU/rcu.rst b/Documentation/RCU/rcu.rst
index 2a830c51477e..0e03c6ef3147 100644
--- a/Documentation/RCU/rcu.rst
+++ b/Documentation/RCU/rcu.rst
@@ -79,7 +79,7 @@ Frequently Asked Questions
Of these, one was allowed to lapse by the assignee, and the
others have been contributed to the Linux kernel under GPL.
There are now also LGPL implementations of user-level RCU
- available (http://liburcu.org/).
+ available (https://liburcu.org/).
- I hear that RCU needs work in order to support realtime kernels?
--
2.17.1
next prev parent reply other threads:[~2020-01-06 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 20:07 [PATCH v3 0/7] Fix trivial nits in RCU docs SeongJae Park
2020-01-06 20:07 ` [PATCH v3 1/7] doc/RCU/Design: Remove remaining HTML tags in ReST files SeongJae Park
2020-01-06 20:07 ` [PATCH v3 2/7] doc/RCU/listRCU: Fix typos in a example code snippets SeongJae Park
2020-01-06 20:07 ` [PATCH v3 3/7] doc/RCU/listRCU: Update example function name SeongJae Park
2020-01-06 20:07 ` [PATCH v3 4/7] doc/RCU/rcu: Use ':ref:' for links to other docs SeongJae Park
2020-01-06 20:08 ` [PATCH v3 5/7] doc/RCU/rcu: Use absolute paths for non-rst files SeongJae Park
2020-01-06 20:08 ` SeongJae Park [this message]
2020-01-06 20:08 ` [PATCH v3 7/7] rcu: Fix typos in beginning comments SeongJae Park
2020-01-07 21:32 ` [PATCH v3 0/7] Fix trivial nits in RCU docs 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=20200106200802.26994-7-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sjpark@amazon.de \
/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).