LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	Geoff Levand <geoff@infradead.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/ps3: Remove unused struct table in setup_areas()
Date: Tue, 28 Jul 2026 15:48:42 +0530	[thread overview]
Message-ID: <23a3df54-dca0-4c98-89e6-9dd89e746b01@linux.ibm.com> (raw)
In-Reply-To: <20260728151342.229f146b-70-amachhiw@linux.ibm.com>


On 7/28/26 3:14 PM, Amit Machhiwal wrote:
> On 2026/07/28 11:32 AM, Madhavan Srinivasan wrote:
>> On 7/27/26 6:47 PM, Christophe Leroy (CS GROUP) wrote:
>>>
>>> Le 12/07/2026 à 17:13, Thorsten Blum a écrit :
>>>> 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>
>>> Looks like it's never been used since commit de91a5342995 ("[POWERPC]
>>> ps3: add spu support") that introduced it.
>>>
>>>
>>> Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
>>>
>>> I have no opinion about the %0 versus 0, is it worth the change ?
>> FYI.. I have added this patch as-is to my fixes-test
>> not waiting for v2
> The v2 was already sent Maddy.
>
>    https://lore.kernel.org/all/20260713091731.97212-3-thorsten.blum@linux.dev/
yes I have picked up the v2. My bad, sorry for the noise
Maddy
> Thanks,
> Amit
>
>> Maddy
>>>
>>>> ---
>>>>    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.
>>>>     */
>>>>      static int __init setup_areas(struct spu *spu)
>>>>    {
>>>> -    struct table {char* name; unsigned long addr; unsigned long size;};
>>>> -
>>>>        spu_pdata(spu)->shadow = ioremap_prot(spu_pdata(spu)->shadow_addr,
>>>>                              sizeof(struct spe_shadow),
>>>> pgprot_noncached_wc(PAGE_KERNEL_RO));


      reply	other threads:[~2026-07-28 10:19 UTC|newest]

Thread overview: 8+ 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
2026-07-27 13:17 ` Christophe Leroy (CS GROUP)
2026-07-28  6:02   ` Madhavan Srinivasan
2026-07-28  9:44     ` Amit Machhiwal
2026-07-28 10:18       ` Madhavan Srinivasan [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=23a3df54-dca0-4c98-89e6-9dd89e746b01@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=geoff@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=thorsten.blum@linux.dev \
    /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