From: Akira Yokosawa <akiyks@gmail.com>
To: ignacio@iencinas.com
Cc: corbet@lwn.net, dvyukov@google.com, elver@google.com,
kasan-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
workflows@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] Documentation: kcsan: fix "Plain Accesses and Data Races" URL in kcsan.rst
Date: Sat, 15 Mar 2025 11:41:03 +0900 [thread overview]
Message-ID: <c6a697af-281a-4a91-8885-a4478dfe2cef@gmail.com> (raw)
In-Reply-To: <1d66a62e-faee-4604-9136-f90eddcfa7c0@iencinas.com>
Hello,
Ignacio Encinas Rubio wrote:
> On 12/3/25 23:36, Jonathan Corbet wrote:
>> It would be best, of course, to get the memory-model documentation
>> properly into our built docs...someday...
>
> I hadn't thought about this. If this sentiment is shared by the LKMM
> people I would be happy to work on this. Has this ever been
> proposed/discussed before?
>
This might be something Jon would like to keep secret, but ...
See the message and the thread it belongs at:
https://lore.kernel.org/lkml/Pine.LNX.4.44L0.1907310947340.1497-100000@iolanthe.rowland.org/
It happened in 2019 responding to Mauro's attempt to conversion of
LKMM docs.
I haven't see any change in sentiment among LKMM maintainers since.
Your way forward would be to keep those .txt files *pure plain text"
and to convert them on-the-fly into reST. Of course only if such an
effort sounds worthwhile to you.
Another approach might be to include those docs literally.
Similar approach has applied to
Documentation/
atomic_t.txt
atomic_bitops.txt
memory-barriers.txt
Regards,
Akira
next prev parent reply other threads:[~2025-03-15 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:11 Ignacio Encinas
2025-03-12 22:36 ` Jonathan Corbet
2025-03-14 16:30 ` Ignacio Encinas Rubio
2025-03-15 2:41 ` Akira Yokosawa [this message]
2025-03-15 12:21 ` Ignacio Encinas Rubio
2025-03-17 23:03 ` Jonathan Corbet
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=c6a697af-281a-4a91-8885-a4478dfe2cef@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=ignacio@iencinas.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.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