From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] scripts/get_feat.pl: allow output the parsed file names
Date: Sat, 26 Mar 2022 11:24:15 +0100 [thread overview]
Message-ID: <20220326112415.444f34af@coco.lan> (raw)
In-Reply-To: <874k3ld1j2.fsf@meer.lwn.net>
Em Fri, 25 Mar 2022 18:02:09 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab@kernel.org> writes:
>
> > Btw, maybe we could replace them tree with a Sphinx comment, like:
> >
> > get_feat.pl:
> > .. FILE <file_name>
> > kernel-doc:
> > .. LINE <line_number>
> > get_abi.pl:
> > .. FILE_LINE <file_name>:<line_number>
> >
> > (or something similar)
> >
> > Just let me know what you prefer and I can take care of the needed
> > changes on this patch and, if it is the case, writing the extra patches
> > in order to use the same model on kernel-doc and get_abi.pl.
>
> If it were just me, I'd just put "FILE <name>" or something simple.
This won't be a problem here, but I would prefer to use something that
would have zero chances of causing issues at kernel-doc and on other
similar scripts that we might end needing. Using a valid ReST tag like
starting it with ".." should fulfill such goal.
A side effect is that the output of the script would be a valid ReST file,
either with or without file/line information, which sounds a good idea
on my eyes.
> I don't really have a strong opinion on the matter though; it's not like
> people have to actually look at these things.
Yes. That's why I ended using #define, the actual meta-tag won't matter
for people.
> I was mostly curious as
> to why you'd done it that way. I can take the original patches or any
> of the variants above; just let me know which you like best and we'll
> get this done.
Ok. I'll resubmit the patch changing to the comments tag. I'll add
patches also for kernel-doc and get_abi.pl for all of them to use
the same meta-tag.
Thanks,
Mauro
next prev parent reply other threads:[~2022-03-26 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 14:05 [PATCH v2 0/4] Better handle dependencies on Sphinx extensions Mauro Carvalho Chehab
2022-03-25 14:05 ` [PATCH v2 1/4] scripts/get_feat.pl: allow output the parsed file names Mauro Carvalho Chehab
2022-03-25 19:19 ` Jonathan Corbet
2022-03-25 23:21 ` Mauro Carvalho Chehab
2022-03-25 23:30 ` Mauro Carvalho Chehab
2022-03-26 0:02 ` Jonathan Corbet
2022-03-26 10:24 ` Mauro Carvalho Chehab [this message]
2022-03-25 14:05 ` [PATCH v2 2/4] docs: kernel_abi.py: add sphinx build dependencies Mauro Carvalho Chehab
2022-03-25 14:05 ` [PATCH v2 3/4] docs: kernel_feat.py: add " Mauro Carvalho Chehab
2022-03-25 14:05 ` [PATCH v2 4/4] docs: kernel_include.py: add sphinx " 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=20220326112415.444f34af@coco.lan \
--to=mchehab@kernel.org \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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