From: Link Mauve <linkmauve@linkmauve.fr>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: "Link Mauve" <linkmauve@linkmauve.fr>,
"Madhavan Srinivasan" <maddy@linux.ibm.com>,
techflashYT <officialTechflashYT@gmail.com>,
"Ash Logan" <ash@heyquark.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] powerpc/sstep: Fix compilation on 32-bit PowerPC
Date: Sun, 20 Sep 2026 19:35:09 +0200 [thread overview]
Message-ID: <arAZTed4p3FYnUgU@desktop> (raw)
In-Reply-To: <3c39b0e5-8265-4d39-ab39-196ccf560a05@kernel.org>
Hi,
On Thu, Jul 30, 2026 at 09:01:10AM +0200, Christophe Leroy (CS GROUP) wrote:
>
>
> Le 30/07/2026 à 08:50, Link Mauve a écrit :
> > Two local variables were only set but never read on 32-bit PowerPC,
> > which causes an error during compilation with W=1.
> >
> > This series first makes the 64-bit guards consistent by converting all
> > uses of __powerpc64__ to use CONFIG_PPC64 instead, and then guard the
> > two variables rc and suffix behind CONFIG_PPC64 checks.
> >
>
> For the two patches,
>
> Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
None of these two patches have made it to any kernel, do I need to ping
someone? I was originally expecting it to reach 7.3, now I guess 7.4
will do.
>
> > Link Mauve (2):
> > powerpc/sstep: Consistently use one define to check arch bit width
> > powerpc/sstep: Don’t define variables we won’t be using
> >
> > arch/powerpc/lib/sstep.c | 111 ++++++++++++++++++++-------------------
> > 1 file changed, 58 insertions(+), 53 deletions(-)
> >
> > Changes since v1:
> > - Link to v1:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Flinuxppc-dev%2Famrpdv0g__ELifId%40desktop%2FT%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C69210bfbc364426c4ce108deee06d0f2%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639209910199709261%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2B%2BdoT%2FTkFxUUy63ED%2B5Kb5dfCSI8hQpjWGfpndI%2Fn0c%3D&reserved=0
> > - Switch from __powerpc64__ to CONFIG_PPC64, as it is the preferred
> > check.
> > - Document that the build error was only occurring with W=1.
> > - Declare both variables on the same line.
> >
> > base-commit: 78bc8af4affb9a732504eb22eeac7d1e50883853
>
Thanks,
--
Link Mauve
next prev parent reply other threads:[~2026-09-20 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 6:50 [PATCH v2 0/2] powerpc/sstep: Fix compilation on 32-bit PowerPC Link Mauve
2026-07-30 6:50 ` [PATCH v2 1/2] powerpc/sstep: Consistently use one define to check arch bit width Link Mauve
2026-07-30 6:50 ` [PATCH v2 2/2] powerpc/sstep: Don’t define variables we won’t be using Link Mauve
2026-07-30 7:01 ` [PATCH v2 0/2] powerpc/sstep: Fix compilation on 32-bit PowerPC Christophe Leroy (CS GROUP)
2026-09-20 17:35 ` Link Mauve [this message]
2026-09-29 11:30 ` Madhavan Srinivasan
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=arAZTed4p3FYnUgU@desktop \
--to=linkmauve@linkmauve.fr \
--cc=ash@heyquark.com \
--cc=chleroy@kernel.org \
--cc=j.neuschaefer@gmx.net \
--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 \
--cc=officialTechflashYT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.