From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
Kees Cook <keescook@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book
Date: Fri, 23 Sep 2022 11:44:50 -0700 [thread overview]
Message-ID: <a22ed923-754a-b757-e0ca-87b6d6e6e8d2@infradead.org> (raw)
In-Reply-To: <20220922204138.153146-8-corbet@lwn.net>
Hi--
On 9/22/22 13:41, Jonathan Corbet wrote:
> These files describe part of the core API, but have never been converted to
> RST due to ... let's say local oppposition. So, create a set of
> special-purpose wrappers to ..include these files into a separate page so
> that they can be a part of the htmldocs build. Then link them into the
> core-api manual and remove them from the "staging" dumping ground.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> ---
> Documentation/core-api/index.rst | 3 ++
> .../core-api/wrappers/atomic_bitops.rst | 18 ++++++++
> Documentation/core-api/wrappers/atomic_t.rst | 19 +++++++++
> .../core-api/wrappers/memory-barriers.rst | 18 ++++++++
> Documentation/staging/index.rst | 42 -------------------
> 5 files changed, 58 insertions(+), 42 deletions(-)
> create mode 100644 Documentation/core-api/wrappers/atomic_bitops.rst
> create mode 100644 Documentation/core-api/wrappers/atomic_t.rst
> create mode 100644 Documentation/core-api/wrappers/memory-barriers.rst
When I look at https://static.lwn.net/kerneldoc/,
I want to move these 3 from "Other documentation":
Atomic Types
Atomic bitops
Memory Barriers
to "Internal API Manuals", then I saw this patch...
Maybe I am misunderstanding. Is this patch supposed to move those 3 items
from Other or not?
thanks.
--
~Randy
next prev parent reply other threads:[~2022-09-23 18:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:41 [PATCH v2 0/4] Rewrite the top-level index.rst Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 1/7] docs: promote the title of process/index.html Jonathan Corbet
2022-09-23 17:53 ` David Vernet
2022-09-23 18:31 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-23 19:02 ` Randy Dunlap
2022-09-23 19:07 ` Jonathan Corbet
2022-09-24 2:05 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-24 2:13 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-24 2:14 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-23 7:45 ` Bagas Sanjaya
2022-09-24 2:10 ` kernel test robot
2022-09-24 2:20 ` David Vernet
2022-09-25 3:54 ` Bagas Sanjaya
2022-09-25 21:29 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 6/7] docs: Expand the front-page CPU-architecture section Jonathan Corbet
2022-09-24 2:25 ` David Vernet
2022-09-25 21:50 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-23 4:25 ` Bagas Sanjaya
2022-09-23 13:39 ` Jonathan Corbet
2022-09-25 3:18 ` Bagas Sanjaya
2022-09-25 3:48 ` Randy Dunlap
2022-09-25 3:52 ` Bagas Sanjaya
2022-09-23 18:44 ` Randy Dunlap [this message]
2022-09-23 19:06 ` Jonathan Corbet
2022-09-23 8:09 ` [PATCH v2 0/4] Rewrite the top-level index.rst Jani Nikula
2022-09-23 8:55 ` Thorsten Leemhuis
2022-09-23 13:45 ` Jonathan Corbet
2022-09-23 14:43 ` Thorsten Leemhuis
2022-09-23 15:03 ` Jonathan Corbet
2022-09-23 17:45 ` Kees Cook
2022-09-24 1:56 ` David Vernet
2022-09-23 18:48 ` Randy Dunlap
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=a22ed923-754a-b757-e0ca-87b6d6e6e8d2@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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®