public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	Geoff Levand <geoff@infradead.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH RESEND 1/2] powerpc/ps3: Drop redundant result assignment
Date: Wed, 18 Mar 2026 15:59:56 +0100	[thread overview]
Message-ID: <ec20e380-e68e-47a9-ace6-6488de14228e@oss.qualcomm.com> (raw)
In-Reply-To: <abqWvBj5_t_Q-y6m@gate>

On 18/03/2026 13:12, Segher Boessenkool wrote:
> On Wed, Mar 18, 2026 at 01:03:03PM +0100, Krzysztof Kozlowski wrote:
>> On 18/03/2026 12:58, Segher Boessenkool wrote:
>>> On Wed, Mar 18, 2026 at 12:54:30PM +0100, Krzysztof Kozlowski wrote:
>>>> On 18/03/2026 12:51, Segher Boessenkool wrote:
>>>>> On Tue, Mar 17, 2026 at 02:08:24PM +0100, Krzysztof Kozlowski wrote:
>>>>>> Return value of ps3_start_probe_thread() is not used, so code can be
>>>>>> simplified to fix W=1 clang warnings:
>>>>>>
>>>>>>   arch/powerpc/platforms/ps3/device-init.c:953:6: error: variable 'result' set but not used [-Werror,-Wunused-but-set-variable]
>>>>>
>>>>> And this is exactly why -Werror is harmful.  A boring harmless warning
>>>>> turned into a build break :-(
>>>>
>>>> -Werror does not matter here. We do not want warnings either, assuming
>>>> of course they are correct.
>>>>
>>>> So if this warning is correct, then patch should be applied and WERROR
>>>> is irrelevant.
>>>
>>> The build is broken.  -Werror is positively harmful.
>>>
>>> Yes, you want the warnings fixed, but maybe something else has priority
>>> right now?
>>
>> What do you mean? This is waiting on the list for long time - note that
>> it is a resend - so if warning is correct, for how long it should wait
>> to get to the "priority" box?
>>
>> And why anything needs even the priority here? Why priority has to be
>> discussed, especially for some legacy (I think?) code? Why correct
>> patches cannot be simply applied after some time/review?
> 
> It is totally simple: without -Werror, you can build a kernel.  With it,
> you cannot.

What are you discussing here? This is a patch, not WERROR talk.

> 
> The ***warning*** is correct, there is something in the code that can be
> improved.  That is why such things are warnings: the compiler can
> produce useful output, there is no reason to scream bloody murder.
> 
> The main reason some people like -Werror is because they are too lazy to
> look at the warning messages they get from normal builds.  Such
> developers need potty training, this is not a reason to punish all more
> reasonable people!
How is this relevant to this warning?

Best regards,
Krzysztof


  reply	other threads:[~2026-03-18 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:08 [PATCH RESEND 1/2] powerpc/ps3: Drop redundant result assignment Krzysztof Kozlowski
2026-03-17 13:08 ` [PATCH RESEND 2/2] powerpc/pasemi: Drop redundant res assignment Krzysztof Kozlowski
2026-03-17 14:32 ` [PATCH RESEND 1/2] powerpc/ps3: Drop redundant result assignment Geert Uytterhoeven
2026-03-18 11:51 ` Segher Boessenkool
2026-03-18 11:54   ` Krzysztof Kozlowski
2026-03-18 11:58     ` Segher Boessenkool
2026-03-18 12:03       ` Krzysztof Kozlowski
2026-03-18 12:12         ` Segher Boessenkool
2026-03-18 14:59           ` Krzysztof Kozlowski [this message]
2026-03-18 12:21       ` Christophe Leroy (CS GROUP)
2026-03-18 15:00         ` Krzysztof Kozlowski

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=ec20e380-e68e-47a9-ace6-6488de14228e@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=chleroy@kernel.org \
    --cc=geoff@infradead.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=llvm@lists.linux.dev \
    --cc=maddy@linux.ibm.com \
    --cc=morbo@google.com \
    --cc=mpe@ellerman.id.au \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=npiggin@gmail.com \
    --cc=segher@kernel.crashing.org \
    /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