From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Shao-Tse Hung <ccs100203@gmail.com>, corbet@lwn.net, paulmck@kernel.org
Cc: frederic@kernel.org, quic_neeraju@quicinc.com,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, rcu@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc/rcu: Update LWN articles at the beginning
Date: Sat, 20 Aug 2022 20:05:47 +0700 [thread overview]
Message-ID: <d63cc303-0b73-4100-829d-01c6e3bb3548@gmail.com> (raw)
In-Reply-To: <20220820083244.28338-1-ccs100203@gmail.com>
On 8/20/22 15:32, Shao-Tse Hung wrote:
> This patch adds LWN articles about RCU APIs which were released in 2019.
> Also, HTTP URLs are replaced by HTTPS.
>
Please write patch description in imperative mood (say "Add 2019 edition
of RCU API documentation and use HTTPS links." instead).
> -| 1. What is RCU, Fundamentally? http://lwn.net/Articles/262464/
> -| 2. What is RCU? Part 2: Usage http://lwn.net/Articles/263130/
> -| 3. RCU part 3: the RCU API http://lwn.net/Articles/264090/
> -| 4. The RCU API, 2010 Edition http://lwn.net/Articles/418853/
> -| 2010 Big API Table http://lwn.net/Articles/419086/
> -| 5. The RCU API, 2014 Edition http://lwn.net/Articles/609904/
> -| 2014 Big API Table http://lwn.net/Articles/609973/
> +| 1. What is RCU, Fundamentally? https://lwn.net/Articles/262464/
> +| 2. What is RCU? Part 2: Usage https://lwn.net/Articles/263130/
> +| 3. RCU part 3: the RCU API https://lwn.net/Articles/264090/
> +| 4. The RCU API, 2010 Edition https://lwn.net/Articles/418853/
> +| 2010 Big API Table https://lwn.net/Articles/419086/
> +| 5. The RCU API, 2014 Edition https://lwn.net/Articles/609904/
> +| 2014 Big API Table https://lwn.net/Articles/609973/
> +| 6. The RCU API, 2019 Edition https://lwn.net/Articles/777036/
> +| 2019 Big API Table https://lwn.net/Articles/777165/
>
I don't think line blocks are necessary for lists. Instead, use nested
list. Why? Big API entry should be as sublist.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-20 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 8:32 Shao-Tse Hung
2022-08-20 13:05 ` Bagas Sanjaya [this message]
2022-08-22 16:44 ` 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=d63cc303-0b73-4100-829d-01c6e3bb3548@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ccs100203@gmail.com \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--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
all inboxes | Powered by JetHome®