From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Christophe Leroy <chleroy@kernel.org>,
Link Mauve <linkmauve@linkmauve.fr>
Cc: 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: Tue, 29 Sep 2026 17:00:58 +0530 [thread overview]
Message-ID: <179066556646.265207.12358872627744720045.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260730065007.964703-1-linkmauve@linkmauve.fr>
On Thu, 30 Jul 2026 08:50:04 +0200, Link Mauve wrote:
> 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.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/sstep: Consistently use one define to check arch bit width
https://git.kernel.org/powerpc/c/a3b88f816f1b87c6dbcbb858d153adb82fec2e15
[2/2] powerpc/sstep: Don’t define variables we won’t be using
https://git.kernel.org/powerpc/c/16736e0587530a2ad074ef716a6a2f1d45f63827
cheers
prev parent reply other threads:[~2026-09-29 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 6:50 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
2026-09-29 11:30 ` 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=179066556646.265207.12358872627744720045.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=ash@heyquark.com \
--cc=chleroy@kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=linkmauve@linkmauve.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®