From: Randy Dunlap <rdunlap@infradead.org>
To: Damien Le Moal <dlemoal@kernel.org>, linux-kernel@vger.kernel.org
Cc: Niklas Cassel <cassel@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata: avoid kernel-doc warnings
Date: Sat, 25 Jul 2026 21:19:04 -0700 [thread overview]
Message-ID: <9eb721f9-ffaf-4bcf-a548-7dd7a8cedf8d@infradead.org> (raw)
In-Reply-To: <4cdc57ad-39a7-42f2-89c2-fab8c06b5da1@kernel.org>
On 7/25/26 9:14 PM, Damien Le Moal wrote:
> On 7/26/26 12:41, Randy Dunlap wrote:
>>
>>
>> On 7/25/26 7:49 PM, Damien Le Moal wrote:
>>> On 7/25/26 10:52, Randy Dunlap wrote:
>>>> Modify comments to prevent kernel-doc warnings:
>>>> - use "/*" for a non-kernel-doc comment
>>>> - add a Returns: section for ata_id_major_version()
>>>>
>>>> Warning: include/linux/ata.h:770 Cannot find identifier on line:
>>>> *
>>>> Warning: include/linux/ata.h:782 function parameter 'id' not described in 'ata_id_sct_data_tables'
>>>> Warning: include/linux/ata.h:782 expecting prototype for Word(). Prototype was for ata_id_sct_data_tables() instead
>>>> Warning: include/linux/ata.h:820 No description found for return value of 'ata_id_major_version'
>>>>
>>>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>>>> ---
>>>> Cc: Damien Le Moal <dlemoal@kernel.org>
>>>> Cc: Niklas Cassel <cassel@kernel.org>
>>>> Cc: linux-ide@vger.kernel.org
>>>>
>>>> include/linux/ata.h | 5 +++--
>>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>>
>>>> --- linux-next-20260722.orig/include/linux/ata.h
>>>> +++ linux-next-20260722/include/linux/ata.h
>>>> @@ -767,8 +767,7 @@ static inline bool ata_id_sense_reportin
>>>> return id[ATA_ID_COMMAND_SET_4] & BIT(6);
>>>> }
>>>>
>>>> -/**
>>>> - *
>>>> +/*
>>>> * Word: 206 - SCT Command Transport
>>>> * 15:12 - Vendor Specific
>>>> * 11:6 - Reserved
>>>> @@ -815,6 +814,8 @@ static inline bool ata_id_sct_supported(
>>>> *
>>>> * The practical impact of this is that ata_id_major_version cannot
>>>> * reliably report on drives below ATA3.
>>>> + *
>>>> + * Returns: major version of ATA drive level or %0 if unknown
>>>
>>> Is the "%0% here intentional ? If yes, why ? Or is it a typo? If it is the
>>> latter, I can fix when applying.
>>
>> It indicates to kernel-doc that it's a constant and should be printed
>> in code/monospace style.
>> But it's perfectly OK to drop it if you prefer that.
>
> Well, given that the patch is all about *not* having that comment as a kernel
> doc, I would prefer staying consistent with this goals and not use kernel docs
> markings. I will remove it if you agree.
> Thanks!
Yes, I see now. Please drop the '%'.
Thanks.
--
~Randy
next prev parent reply other threads:[~2026-07-26 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 1:52 Randy Dunlap
2026-07-26 2:49 ` Damien Le Moal
2026-07-26 3:41 ` Randy Dunlap
2026-07-26 4:14 ` Damien Le Moal
2026-07-26 4:19 ` Randy Dunlap [this message]
2026-07-27 2:02 ` Damien Le Moal
2026-07-27 1:49 ` Damien Le Moal
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=9eb721f9-ffaf-4bcf-a548-7dd7a8cedf8d@infradead.org \
--to=rdunlap@infradead.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@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
all inboxes | Powered by JetHome®