From: Thorsten Blum <thorsten.blum@linux.dev>
To: Geoff Levand <geoff@infradead.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/ps3: Remove unused struct table in setup_areas()
Date: Mon, 13 Jul 2026 11:02:29 +0200 [thread overview]
Message-ID: <alSppS3b9IzhlUIs@linux.dev> (raw)
In-Reply-To: <20260713134356.62f55781-f6-amachhiw@linux.ibm.com>
On Mon, Jul 13, 2026 at 01:59:02PM +0530, Amit Machhiwal wrote:
> On 2026/07/12 05:13 PM, Thorsten Blum wrote:
> > The local table structure is not used - remove it.
> >
> > Remove % in the comment while at it.
> >
> > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> > ---
> > arch/powerpc/platforms/ps3/spu.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/arch/powerpc/platforms/ps3/spu.c b/arch/powerpc/platforms/ps3/spu.c
> > index e817def7f424..c904f9fa1caa 100644
> > --- a/arch/powerpc/platforms/ps3/spu.c
> > +++ b/arch/powerpc/platforms/ps3/spu.c
> > @@ -185,13 +185,11 @@ static void spu_unmap(struct spu *spu)
> > * The current HV requires the spu shadow regs to be mapped with the
> > * PTE page protection bits set as read-only.
> > *
> > - * Returns: %0 on success or -errno on error.
> > + * Returns: 0 on success or -errno on error.
>
> The % prefix should actually be kept here I think. Per the kernel-doc
> documentation [1]:
>
> %CONST
> Name of a constant. (No cross-referencing, just formatting.)
>
> Examples:
>
> %0 %NULL %-1 %-EFAULT %-EINVAL %-ENOMEM
>
> So %0 is valid and intentional kernel-doc markup that renders the
> constant 0 with proper formatting.
Interesting - not sure I have seen this style before and plain 0 seems
to be far more common. There has been some discussion around it here:
https://lore.kernel.org/all/87ilamz4j5.fsf@meer.lwn.net/
I guess I'll send a v2 without the %0 change.
Thanks,
Thorsten
prev parent reply other threads:[~2026-07-13 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 15:13 [PATCH] powerpc/ps3: Remove unused struct table in setup_areas() Thorsten Blum
2026-07-13 7:25 ` Geert Uytterhoeven
2026-07-13 8:29 ` Amit Machhiwal
2026-07-13 9:02 ` Thorsten Blum [this message]
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=alSppS3b9IzhlUIs@linux.dev \
--to=thorsten.blum@linux.dev \
--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 \
--cc=npiggin@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