From: Alex Shi <alex.shi@linux.alibaba.com>
To: Joe Perches <joe@perches.com>, andrew@lunn.ch
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/dsa: remove unused macros to tame gcc warning
Date: Fri, 6 Nov 2020 16:57:29 +0800 [thread overview]
Message-ID: <28a5c53a-a576-7884-85ae-2adba39f2b8f@linux.alibaba.com> (raw)
In-Reply-To: <1662b333dd72369af4c1173035d43590fbc45292.camel@perches.com>
在 2020/11/6 下午4:52, Joe Perches 写道:
> On Fri, 2020-11-06 at 16:28 +0800, Alex Shi wrote:
>>
>> 在 2020/11/6 下午2:36, Joe Perches 写道:
>>> On Fri, 2020-11-06 at 13:37 +0800, Alex Shi wrote:
>>>> There are some macros unused, they causes much gcc warnings. Let's
>>>> remove them to tame gcc.
>>>
>>> I believe these to be essentially poor warnings.
>>>
>>> Aren't these warnings generated only when adding W=2 to the make
>>> command line?
>>>
>>> Perhaps it's better to move the warning to level 3
>>> ---
>>> diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn
>>> index 95e4cdb94fe9..5c3c220ddb32 100644
>>> --- a/scripts/Makefile.extrawarn
>>> +++ b/scripts/Makefile.extrawarn
>>> @@ -68,7 +68,6 @@ KBUILD_CFLAGS += $(call cc-option, -Wlogical-op)
>>> KBUILD_CFLAGS += -Wmissing-field-initializers
>>> KBUILD_CFLAGS += -Wtype-limits
>>> KBUILD_CFLAGS += $(call cc-option, -Wmaybe-uninitialized)
>>> -KBUILD_CFLAGS += $(call cc-option, -Wunused-macros)
>>
>> This changed too much, and impact others. May not good. :)
>
> Can you clarify what you mean?
>
Uh, change in this file will impact all kernels not only for net/dsa.
If you want to keep these unused macros, maybe better to put them into comments?
Thanks!
Alex
next prev parent reply other threads:[~2020-11-06 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 5:37 Alex Shi
2020-11-06 6:36 ` Joe Perches
2020-11-06 8:28 ` Alex Shi
2020-11-06 8:52 ` Joe Perches
2020-11-06 8:57 ` Alex Shi [this message]
2020-11-06 9:24 ` David Laight
2020-11-06 14:18 ` Andrew Lunn
2020-11-06 16:39 ` Florian Fainelli
2020-11-07 12:54 ` Alex Shi
2020-11-07 17:39 ` Joe Perches
2020-11-07 22:33 ` Andrew Lunn
2020-11-08 12:39 ` David Laight
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=28a5c53a-a576-7884-85ae-2adba39f2b8f@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@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®