From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Convert get_feat to Python
Date: Fri, 21 Nov 2025 22:27:36 +0100 [thread overview]
Message-ID: <20251121222736.205d2a3f@foz.lan> (raw)
In-Reply-To: <87jyzjth1j.fsf@trenco.lwn.net>
Em Fri, 21 Nov 2025 10:46:32 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
> So you had me worried with this:
>
> > As we don't have a definition yet for the location of the Python
> > libraries yet, I opted to place the parse features library inside
> > tools/docs/lib. It shouldn't be hard to move it elsewhere once we
> > define a better place for them.
>
> But it seems that you did, in fact, update the library location.
Heh, forgot to update the description ;-)
> I've
> applied these, thanks.
Thanks!
Mauro
prev parent reply other threads:[~2025-11-21 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 19:09 [PATCH v2 0/3] Convert get_feat to Python Mauro Carvalho Chehab
2025-11-18 19:09 ` [PATCH v2 1/3] tools/docs/get_feat.py: convert get_feat.pl " Mauro Carvalho Chehab
2025-11-18 19:09 ` [PATCH v2 2/3] Documentation/sphinx/kernel_feat.py: use class directly Mauro Carvalho Chehab
2025-11-18 19:09 ` [PATCH v2 3/3] get_feat.pl: remove it, as it got replaced by get_feat.py Mauro Carvalho Chehab
2025-11-21 17:46 ` [PATCH v2 0/3] Convert get_feat to Python Jonathan Corbet
2025-11-21 21:27 ` Mauro Carvalho Chehab [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=20251121222736.205d2a3f@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).