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: Thu, 26 Feb 2026 11:19:44 -0800 [thread overview]
Message-ID: <8ef1def3-afa7-416a-af42-bf4324fc788a@infradead.org> (raw)
In-Reply-To: <c4a9ba45-24d5-474f-968f-a9dde81d3303@kernel.org>
On 2/26/26 3:58 AM, Christophe Leroy (CS GROUP) wrote:
>
>
> Le 26/02/2026 à 02:45, Randy Dunlap a écrit :
>>
>>
>> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.ozlabs.org%2Fproject%2Flinuxppc-dev%2Fpatch%2F20251129183636.1893634-1-rdunlap%40infradead.org%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C5f40eabfbf95474b6c4608de74d8ad0e%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639076671142017726%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Bk2srZQMhhrA6rpHEFx2CIxSee8%2FUM2TIrNQSFpP8%2B4%3D&reserved=0
>>>
>>> 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.
>>
>
> Ok so I reject that one.
ack.
> Here is the list of patches from you we have in the pipe:
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=18663
Looks good. Thanks.
--
~Randy
next prev parent reply other threads:[~2026-02-26 19:19 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
2026-02-26 11:58 ` Christophe Leroy (CS GROUP)
2026-02-26 19:19 ` Randy Dunlap [this message]
-- 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=8ef1def3-afa7-416a-af42-bf4324fc788a@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