public inbox for lkmm@lists.linux.dev
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	"Paul E. McKenney" <paulmck@kernel.org>
Cc: mchehab+huawei@kernel.org, joel@joelfernandes.org,
	linux-kernel-mentees@lists.linux.dev, peterz@infradead.org,
	stern@rowland.harvard.edu, Shuah Khan <skhan@linuxfoundation.org>,
	Ignacio Encinas Rubio <ignacio@iencinas.com>,
	lkmm@lists.linux.dev, Marco Elver <elver@google.com>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] lkmm: docs: Put LKMM documentation into dev-tools book
Date: Tue, 10 Jun 2025 11:11:50 +0900	[thread overview]
Message-ID: <c1e93b99-21a1-4646-af6c-e05330e1cd3d@gmail.com> (raw)
In-Reply-To: <87ikl48te3.fsf@trenco.lwn.net>

On Mon, 09 Jun 2025 16:03:32 -0600, Jonathan Corbet wrote:
> Akira Yokosawa <akiyks@gmail.com> writes:
> 
>> Currently, LKMM docs are not included in any of kernel documentation
>> books.
>>
>> Commit e40573a43d16 ("docs: put atomic*.txt and memory-barriers.txt
>> into the core-api book") covered plain-text docs under Documentation/
>> by using the "include::" directive along with the ":literal:" option.
>>
>> As LKMM docs are not under Documentation/, the same approach would not
>> work due to the limit of the include:: directive. 
>>
>> As a matter of fact, kernel documentation has an extended directive
>> by the name of "kernel-include::", which has no such limitation.
>>
>> Rather than moving LKMM docs around, use the latter with source tree's
>> abspath passed through via the "SOURCEDIR" variable which is now defined
>> in Documentation/Makefile, and make them included in the dev-tools book
>> next to KCSAN.
> 
> So this fell through the cracks during my May travel, sorry.

Thank you for taking the time!

> 
> I've taken a look at it now ... it adds a vast number of build warnings:
> 
> Documentation/networking/netlink_spec/rt_addr.rst:28: WARNING: duplicate label rt-addr-operation-newaddr, other instance in /stuff/k/git/kernel/Documentation/networking/netlink_spec/rt-addr.rst
> Documentation/networking/netlink_spec/rt_addr.rst:41: WARNING: duplicate label rt-addr-operation-deladdr, other instance in /stuff/k/git/kernel/Documentation/networking/netlink_spec/rt-addr.rst
> Documentation/networking/netlink_spec/rt_addr.rst:54: WARNING: duplicate label rt-addr-operation-getaddr, other instance in /stuff/k/git/kernel/Documentation/networking/netlink_spec/rt-addr.rst
> [...]
> 
> I haven't had a chance to figure out *why* it would have this particular
> bizarre effect...

I don't think those new warnings have anything to do with this patch.

This is mentioned by Paolo at:
  https://lore.kernel.org/495e43ef-ae20-4dda-97c0-cb8ebe97394b@redhat.com/

    My understanding is that this rename triggers rebuild of the related
    doc, which in turns leads to quite a large number of htmldoc warning,
    but it's really unharmful/pre-existing issue.

, and Donald said in his reply at:
  https://lore.kernel.org/CAD4GDZw+Enkd2dA8f7pNxMadwURFd_tHv1sUwkXqFqxsOquHQQ@mail.gmail.com/

    Yes, Documentation/Makefile goes the extra mile to only try deleting a
    list of .rst files generated from the list of source .yaml files. It
    would be easier to just delete
    Documentation/networking/netlink_spec/*.rst which would be able to
    clean up old generated files in situations like this.

HTH.

BTW, I assumed Paul would take this patch into his lkmm branch for v6.17,
once all is clear for the new uses of "..kernel-include::" with ":literal:".

Thanks,
Akira

  reply	other threads:[~2025-06-10  2:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-30 11:07 Potential translation of LKMM docs into ReST Ignacio Encinas Rubio
2025-03-30 16:09 ` Alan Stern
2025-03-30 17:52   ` Mauro Carvalho Chehab
2025-05-06  2:50 ` [PATCH] lkmm: docs: Put LKMM documentation into dev-tools book Akira Yokosawa
2025-05-07  0:07   ` Paul E. McKenney
2025-06-09 22:03   ` Jonathan Corbet
2025-06-10  2:11     ` Akira Yokosawa [this message]
2025-06-10  8:13       ` Mauro Carvalho Chehab

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=c1e93b99-21a1-4646-af6c-e05330e1cd3d@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=elver@google.com \
    --cc=ignacio@iencinas.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=lkmm@lists.linux.dev \
    --cc=mchehab+huawei@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=stern@rowland.harvard.edu \
    /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