From: Akira Yokosawa <akiyks@gmail.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: viresh.kumar@linaro.org, linux-kernel@vger.kernel.org,
linux@rasmusvillemoes.dk, vincent.guittot@linaro.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 1/2] cpumask: Fix kernel-doc formatting errors in cpumask.h
Date: Fri, 7 Mar 2025 10:06:38 +0900 [thread overview]
Message-ID: <638eee89-dd74-4a7a-b780-03ac53860098@gmail.com> (raw)
In-Reply-To: <Z8njHKwzQXdaUAjD@thinkpad>
Hi,
Yury Norov wrote:
> On Fri, Mar 07, 2025 at 12:38:41AM +0900, Akira Yokosawa wrote:
>> Hello Viresh,
>>
>> On Thu, 6 Mar 2025 16:06:50 +0530, Viresh Kumar wrote:
>>> This fixes various kernel-doc formatting errors in cpumask.h:
>>>
>>> - WARNING: Inline literal start-string without end-string.
>>> - ERROR: Unexpected indentation.
>>> - ERROR: Unknown target name: "gfp".
>>>
>>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>>> ---
>>> include/linux/cpumask.h | 65 +++++++++++++++++++++++------------------
>>> 1 file changed, 37 insertions(+), 28 deletions(-)
>>>
>>> diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
>>> index 36a890d0dd57..73ba808c559f 100644
>>> --- a/include/linux/cpumask.h
>>> +++ b/include/linux/cpumask.h
>>> @@ -20,7 +20,7 @@
>>> * cpumask_pr_args - printf args to output a cpumask
>>> * @maskp: cpumask to be printed
>>> *
>>> - * Can be used to provide arguments for '%*pb[l]' when printing a cpumask.
>>> + * Can be used to provide arguments for '\%*pb[l]' when printing a cpumask.
>>
>> kernel-doc (script) can recognize the pattern of %*pb but not %*pb[l].
>> "%*bp [l]" should work here.
>> (without quotes and a white space in front of "[").
>
> So why not fixing kernel-doc instead?
That would be great!
At the moment, re-implementation of kernel-doc into python is under way [1].
[1]: https://lore.kernel.org/cover.1740387599.git.mchehab+huawei@kernel.org/
It is a bug compatible porting from perl to python3, but it is likely
to be merged during 6.16 merge window.
I think it would be nicer to do the fix on top of python3 kernel-doc
after that happens.
Thanks, Akira
>
>> No need to escape "%".
>>
>>> */
>>> #define cpumask_pr_args(maskp) nr_cpu_ids, cpumask_bits(maskp)
>>>
[...]
next prev parent reply other threads:[~2025-03-07 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 10:36 [PATCH 0/2] docs: core-api: Update kernel-api.rst to include cpumask.h Viresh Kumar
2025-03-06 10:36 ` [PATCH 1/2] cpumask: Fix kernel-doc formatting errors in cpumask.h Viresh Kumar
2025-03-06 15:38 ` Akira Yokosawa
2025-03-06 18:02 ` Yury Norov
2025-03-07 1:06 ` Akira Yokosawa [this message]
2025-03-07 7:35 ` Viresh Kumar
2025-03-06 10:36 ` [PATCH 2/2] docs: core-api: Update kernel-api.rst to include cpumask.h Viresh Kumar
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=638eee89-dd74-4a7a-b780-03ac53860098@gmail.com \
--to=akiyks@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=yury.norov@gmail.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