From: Johannes Berg <johannes@sipsolutions.net>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bitfield: avoid gcc-8 -Wint-in-bool-context warning
Date: Tue, 14 Aug 2018 09:56:45 +0200 [thread overview]
Message-ID: <1534233405.3547.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CAK7LNASVE-vZhGyAsWg8YmPb8P-sucwPVOUt5qsfVwZQuHg9gw@mail.gmail.com>
On Tue, 2018-08-14 at 08:57 +0900, Masahiro Yamada wrote:
> 2018-08-14 7:09 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > Passing an enum into FIELD_GET() produces a long but harmless warning on
> > newer compilers:
> >
> > from include/linux/linkage.h:7,
> > from include/linux/kernel.h:7,
> > from include/linux/skbuff.h:17,
> > from include/linux/if_ether.h:23,
> > from include/linux/etherdevice.h:25,
> > from drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c:63:
> > drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c: In function 'iwl_mvm_rx_mpdu_mq':
> > include/linux/bitfield.h:56:20: error: enum constant in boolean context [-Werror=int-in-bool-context]
> > BUILD_BUG_ON_MSG(!(_mask), _pfx "mask is zero"); \
> > ^
> > ...
> > include/linux/bitfield.h:103:3: note: in expansion of macro '__BF_FIELD_CHECK'
> > __BF_FIELD_CHECK(_mask, _reg, 0U, "FIELD_GET: "); \
> > ^~~~~~~~~~~~~~~~
> > drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c:1025:21: note: in expansion of macro 'FIELD_GET'
> > le16_encode_bits(FIELD_GET(IWL_RX_HE_PHY_SIBG_SYM_OR_USER_NUM_MASK,
>
>
> How about fixing the root cause
> in drivers/net/wireless/intel/iwlwifi/fw/api/rx.h ?
>
>
> #define IWL_RX_HE_PHY_SIBG_SYM_OR_USER_NUM_MASK 0x1e00000000ULL
>
>
> enum iwl_rx_he_phy looks really strange.
Why? I don't think this is a problem, the enum is used here to get
constants so that we can also have documentation for them. That's a
common and accepted technique.
> Passing enum to FIELD_GET is odd,
> so I prefer keeping this warned.
What for?
I think we should go with Arend's patch, and I hope Andrew will pick it
up, but otherwise I guess we can also put it through any other tree.
johannes
next prev parent reply other threads:[~2018-08-14 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 22:09 [PATCH] bitfield: avoid gcc-8 -Wint-in-bool-context warning Arnd Bergmann
2018-08-13 23:57 ` Masahiro Yamada
2018-08-14 7:56 ` Johannes Berg [this message]
2018-08-14 8:43 ` Arnd Bergmann
2018-08-14 9:31 ` Masahiro Yamada
2018-08-14 10:06 ` David Laight
2018-08-14 11:08 ` Arnd Bergmann
2018-08-14 11:10 ` Johannes Berg
2018-08-14 13:09 ` David Laight
2018-08-14 23:11 ` Andrew Morton
2018-08-14 23:13 ` Andrew Morton
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=1534233405.3547.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=jakub.kicinski@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).