From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Convert get_feat to Python
Date: Tue, 11 Nov 2025 23:12:32 +0100 [thread overview]
Message-ID: <20251111231232.3955f1fb@foz.lan> (raw)
In-Reply-To: <87a50swl6d.fsf@trenco.lwn.net>
Em Tue, 11 Nov 2025 10:09:30 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
> > Hi Jon,
> >
> > That's the final series to complete the migration of documentation
> > build: it converts get_feat from Perl to Python.
> >
> > With that, no Sphinx in-kernel extensions use fork anymore to call
> > ancillary scripts: everything is now importing Python methods
> > directly from the libraries.
>
> This, of course, conflicts with my library move ... Maybe we review
> that and I go first this time? :)
Sure, go ahead with the library move, while this is reviewed.
This one is trivial enough to be rebased on the top of it.
Thanks,
Mauro
next prev parent reply other threads:[~2025-11-11 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 16:17 [PATCH 0/3] Convert get_feat to Python Mauro Carvalho Chehab
2025-11-11 16:17 ` [PATCH 1/3] tools/docs/get_feat.py: convert get_feat.pl " Mauro Carvalho Chehab
2025-11-11 16:17 ` [PATCH 2/3] Documentation/sphinx/kernel_feat.py: use class directly Mauro Carvalho Chehab
2025-11-11 16:17 ` [PATCH 3/3] get_feat.pl: remove it, as it got replaced by get_feat.py Mauro Carvalho Chehab
2025-11-11 17:09 ` [PATCH 0/3] Convert get_feat to Python Jonathan Corbet
2025-11-11 22:12 ` Mauro Carvalho Chehab [this message]
2025-11-18 16:44 ` Jonathan Corbet
2025-11-18 19:10 ` 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=20251111231232.3955f1fb@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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