From: Randy Dunlap <rdunlap@infradead.org>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Geoff Levand <geoff@infradead.org>,
linuxppc-dev@lists.ozlabs.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] powerpc/ps3: fix ps3.h kernel-doc warnings
Date: Wed, 25 Feb 2026 17:45:03 -0800 [thread overview]
Message-ID: <17c0c331-276b-4f43-890e-39fb3010103c@infradead.org> (raw)
In-Reply-To: <4e84b9ea-9e7b-420a-bca9-6febd87a80cb@kernel.org>
On 2/24/26 10:57 PM, Christophe Leroy (CS GROUP) wrote:
> Hi Randy,
>
> Le 22/02/2026 à 07:01, Randy Dunlap a écrit :
>> Eliminate all kernel-doc warnings in ps3.h:
>> - add one missing struct member description
>> - add one missing function short description
>> - correct one enum name typo
>> - change several incomplete kernel-doc comments to plain "/*" comments
>>
>> Examples:
>>
>> Warning: arch/powerpc/include/asm/ps3.h:96 struct member 'dev' not
>> described in 'ps3_dma_region'
>> Warning: arch/powerpc/include/asm/ps3.h:408 missing initial short
>> description on line: * ps3_system_bus_set_drvdata -
>> Warning: arch/powerpc/include/asm/ps3.h:473 Enum value
>> 'PS3_LPM_TB_TYPE_INTERNAL' not described in enum 'ps3_lpm_tb_type'
>> Warning: arch/powerpc/include/asm/ps3.h:473 Excess enum value
>> '@PS3_LPM_RIGHTS_USE_TB' description in 'ps3_lpm_tb_type'
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>
> You sent a V2 with the same subject some time ago, see https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20251129183636.1893634-1-rdunlap@infradead.org/
>
> Is this patch something else, does it superseeds V2, or is it a wrong resend of V1 ?
Yup, it's a wrong resend of v1. It means that my patch tracking system
failed me. Sorry about that.
--
~Randy
next prev parent reply other threads:[~2026-02-26 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 6:01 [PATCH] powerpc/ps3: fix ps3.h kernel-doc warnings Randy Dunlap
2026-02-25 6:57 ` Christophe Leroy (CS GROUP)
2026-02-26 1:45 ` Randy Dunlap [this message]
2026-02-26 11:58 ` Christophe Leroy (CS GROUP)
2026-02-26 19:19 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-11-29 0:24 Randy Dunlap
2025-11-29 5:51 ` Randy Dunlap
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=17c0c331-276b-4f43-890e-39fb3010103c@infradead.org \
--to=rdunlap@infradead.org \
--cc=chleroy@kernel.org \
--cc=geoff@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.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