From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <mchehab+huawei@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Bingbu Cao <bingbu.cao@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <mchehab+huawei@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-arch@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 00/39] Implement kernel-doc in Python
Date: Mon, 24 Feb 2025 16:49:10 -0700 [thread overview]
Message-ID: <87msea29ah.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1740387599.git.mchehab+huawei@kernel.org>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Hi Jon,
>
> This changeset contains the kernel-doc.py script to replace the verable
> kernel-doc originally written in Perl. It replaces the first version and the
> second series I sent on the top of it.
I've sent minor comments on a couple of the patches. The new version
works for me, I can't find any real problems with it.
Here's the question: what were your thoughts on when to do this? I can
certainly take the initial fixup patches and get them out of your queue,
but at some point there will be a need to dive into the deep end. I'm
just a bit leery of doing that as we head toward -rc5... what do you
think of "just after the merge window"?
I'm definitely looking forward to no longer having to bash my head
against the Perl version...
Thanks,
jon
next prev parent reply other threads:[~2025-02-24 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 9:08 [PATCH v2 00/39] Implement kernel-doc in Python Mauro Carvalho Chehab
2025-02-24 9:08 ` [PATCH v2 02/39] drivers: media: intel-ipu3.h: fix identation on a kernel-doc markup Mauro Carvalho Chehab
2025-02-24 23:49 ` Jonathan Corbet [this message]
2025-02-25 7:54 ` [PATCH v2 00/39] Implement kernel-doc in Python Mauro Carvalho Chehab
2025-02-25 14:33 ` 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=87msea29ah.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=arnd@arndb.de \
--cc=bingbu.cao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mchehab+huawei@kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox