All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	John Garry <john.garry@huawei.com>
Cc: <linux-ide@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ata: pata_cs5535: Fix W=1 warnings
Date: Tue, 28 Jun 2022 13:05:26 +0300	[thread overview]
Message-ID: <9044b81f-76db-75de-db74-f45d6e5ea71e@omp.ru> (raw)
In-Reply-To: <16f727b8-c3b0-c828-0c5b-6728a6e7934f@opensource.wdc.com>

Hello!

On 6/28/22 11:59 AM, Damien Le Moal wrote:
[...]
>> x86_64 allmodconfig build with W=1 gives these warnings:
>>
>> drivers/ata/pata_cs5535.c: In function ‘cs5535_set_piomode’:
>> drivers/ata/pata_cs5535.c:93:11: error: variable ‘dummy’ set but not used [-Werror=unused-but-set-variable]
>>   u32 reg, dummy;
>>            ^~~~~
>> drivers/ata/pata_cs5535.c: In function ‘cs5535_set_dmamode’:
>> drivers/ata/pata_cs5535.c:132:11: error: variable ‘dummy’ set but not used [-Werror=unused-but-set-variable]
>>   u32 reg, dummy;
>>            ^~~~~
>> cc1: all warnings being treated as errors
>>
>> Mark variables 'dummy' as "maybe unused" to satisfy when rdmsr() is
>> stubbed, which is the same as what we already do in pata_cs5536.c .
>>
>> Signed-off-by: John Garry <john.garry@huawei.com>


Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>

> Looks good, but I wonder why I am not getting this warning. I always do
> W=1 and C=1 builds. I tried allmodconfig now and I am not getting the
> warning...

   I can confirm the (fatal) warnings with RedHat gcc 10.3.1... but somehow they only
occur on x86_64 with allmodconfig indeed (which is strange)...

[...]

MBR, Sergey


  parent reply	other threads:[~2022-06-28 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 13:12 [PATCH] ata: pata_cs5535: Fix W=1 warnings John Garry
2022-06-28  8:59 ` Damien Le Moal
2022-06-28  9:27   ` John Garry
2022-06-28 10:05   ` Sergey Shtylyov [this message]
2022-06-28 18:39     ` Sergey Shtylyov
2022-06-29  7:41       ` John Garry
2022-06-29  8:24         ` Damien Le Moal
2022-06-29  1:14     ` Damien Le Moal
2022-06-29  1:51 ` Damien Le Moal
2022-06-29 13:32   ` Sergey Shtylyov
2022-06-29 23:03     ` Damien Le Moal

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=9044b81f-76db-75de-db74-f45d6e5ea71e@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=john.garry@huawei.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.