From: Jonathan Corbet <corbet@lwn.net>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Dongliang Mu <dzm91@hust.edu.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: parse-headers: Fix script name and stale Makefile reference
Date: Mon, 07 Sep 2026 10:02:39 -0600 [thread overview]
Message-ID: <875x0hvylc.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260905025821.83968-1-kmehltretter@gmail.com>
Karl Mehltretter <kmehltretter@gmail.com> writes:
> The script is tools/docs/parse-headers.py, not parse_headers.py, and its
> FILE_RULES argument is optional. Commit 8a298579cdfc ("scripts:
> sphinx-build-wrapper: get rid of uapi/media Makefile") removed the
> Makefile the text points to as an example; the cross-references are now
> generated by the kernel-include directive, so point to a file that uses
> it.
>
> Fixes: d69a03a97a2d ("docs: doc-guide: parse-headers.rst update its documentation")
> Fixes: 8a298579cdfc ("scripts: sphinx-build-wrapper: get rid of uapi/media Makefile")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
> Documentation/doc-guide/parse-headers.rst | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2026-09-07 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 2:58 [PATCH] docs: parse-headers: Fix script name and stale Makefile reference Karl Mehltretter
2026-09-05 3:54 ` Randy Dunlap
2026-09-07 16:02 ` Jonathan Corbet [this message]
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=875x0hvylc.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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