From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH] cpufreq: longrun: fix typo in kernel-doc
Date: Tue, 20 Oct 2026 11:47:00 +0800 [thread overview]
Message-ID: <d2c3fa0a-348b-4015-b2c9-b97d8c7964c8@oss.qualcomm.com> (raw)
In-Reply-To: <c635054081da35e61ccc25cf356f6356ca8580ba.camel@mailbox.org>
On 10/19/2026 4:51 PM, Manuel Ebner wrote:
> On Mon, 2026-10-19 at 11:37 +0800, Zhongqiu Han wrote:
>> Hi Manuel,
>>
>> Thanks for the patch.
>>
>> On 10/17/2026 3:14 PM, Manuel Ebner wrote:
>>> Fix typo to fix:
>>>
>>> $ ./scripts/kernel-doc -none drivers/cpufreq/longrun.c
>>> Warning: drivers/cpufreq/longrun.c:126 expecting prototype for longrun_verify_poliy(). Prototype was for longrun_verify_policy() instead
>>
>> ./scripts/checkpatch.pl reports a warning which should be acceptable to
>> keep unwrapped as it is tool output.
>>
>> WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit
>> description?)
>> #9:
>> Warning: drivers/cpufreq/longrun.c:126 expecting prototype for
>> longrun_verify_poliy(). Prototype was for longrun_verify_policy() instead
>>
>> total: 0 errors, 1 warnings, 8 lines checked
>>
>>
>>
>> Also, while reproducing this issue, I noticed another problem,
>>
>> ./scripts/kernel-doc -none drivers/cpufreq/longrun.c
>> Warning: drivers/cpufreq/longrun.c:21 This comment starts with '/**',
>> but isn't a kernel-doc comment. Refer to
>> Documentation/doc-guide/kernel-doc.rst
>> * longrun_{low,high}_freq is needed for the conversion of cpufreq kHz
>>
>> It should use /* instead of /** and may be worth a separate patch.
>
> Will do.
Thanks
>
>> But
>> since this patch is only intended to fix the typo, the patch itself
>> looks fine to me.
>>
>>>
>>> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
>>
>> Small nit: please consider to add the Fixes tag:
>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>
> Well, thats the init commit, should it still be added in
> future patches?
> Can pre-git history be referenced?
AFAIK, yes, the usual approach for pre-Git history is to use
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2"), the initial Git commit.
Many patches have used this Fixes tag, for example:
https://lore.kernel.org/all/?q=1da177e4c3f4
>
>>
>> Reviewed-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
>>
>
> Thanks
> Manuel
>
>> ...
--
Thx and BRs,
Zhongqiu Han
next prev parent reply other threads:[~2026-10-20 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 7:14 Manuel Ebner
2026-10-19 3:37 ` Zhongqiu Han
2026-10-19 8:51 ` Manuel Ebner
2026-10-20 3:47 ` Zhongqiu Han [this message]
2026-10-19 6:35 ` 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=d2c3fa0a-348b-4015-b2c9-b97d8c7964c8@oss.qualcomm.com \
--to=zhongqiu.han@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®