From: Kees Cook <kees@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Mike Rapoport <rppt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
Maxime Ripard <mripard@kernel.org>, Tejun Heo <tj@kernel.org>,
Natalie Vock <natalie.vock@gmx.de>, Xavier <xavier_qy@163.com>,
Samuel Holland <samuel.holland@sifive.com>,
Maarten Lankhorst <dev@lankhorst.se>,
Dan Williams <dan.j.williams@intel.com>,
Michael Kelley <mhklinux@outlook.com>,
Kuan-Wei Chiu <visitorckw@gmail.com>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] kernel-doc: Add initial binfmt docs
Date: Tue, 29 Apr 2025 10:28:58 -0700 [thread overview]
Message-ID: <202504291028.523CF77C@keescook> (raw)
In-Reply-To: <87selrrhnw.fsf@trenco.lwn.net>
On Mon, Apr 28, 2025 at 05:27:15PM -0600, Jonathan Corbet wrote:
> Kees Cook <kees@kernel.org> writes:
>
> > Adds a framework to hold the initial exec.c and binfmt_elf.c
> > kernel-docs. Updates scripts/kernel-doc to allow leading whitespace so
> > that embedded "DOC:" tags can be found that aren't at the start of a
> > line so that in-function documentation can be found, like that recently
> > marked up in binfmt_elf.c[1].
>
> Just one tiny little problem ... when you weren't looking, Mauro snuck
> in and replaced scripts/kernel-doc with a shiny new Python
> implementation. So that part of the patch won't apply to docs-next; if
> you apply it somewhere else, the change will get lost.
>
> I figured we were going to run into at least one of these ... sorry ...
Oh duh, yeah, I will go re-do this with -next.
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-04-29 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 0:07 [PATCH] kernel-doc: Add initial binfmt docs Kees Cook
2025-04-28 23:27 ` Jonathan Corbet
2025-04-29 17:28 ` Kees Cook [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=202504291028.523CF77C@keescook \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dev@lankhorst.se \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhklinux@outlook.com \
--cc=mripard@kernel.org \
--cc=natalie.vock@gmx.de \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tj@kernel.org \
--cc=visitorckw@gmail.com \
--cc=xavier_qy@163.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.