netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
	"David S . Miller" <davem@davemloft.net>,
	Simon Horman <simon.horman@netronome.com>,
	Dirk van der Merwe <dirk.vandermerwe@netronome.com>,
	oss-drivers@netronome.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Renato Golin <renato.golin@linaro.org>,
	Manoj Gupta <manojgupta@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH] nfp: convert nfp_eth_set_bit_config() into a macro
Date: Wed, 4 Oct 2017 11:49:57 -0700	[thread overview]
Message-ID: <20171004184957.GO173745@google.com> (raw)
In-Reply-To: <1507140439.4434.14.camel@perches.com>

Hi Joe,

El Wed, Oct 04, 2017 at 11:07:19AM -0700 Joe Perches ha dit:

> On Tue, 2017-10-03 at 13:05 -0700, Matthias Kaehlcke wrote:
> > nfp_eth_set_bit_config() is marked as __always_inline to allow gcc to
> > identify the 'mask' parameter as known to be constant at compile time,
> > which is required to use the FIELD_GET() macro.
> > 
> > The forced inlining does the trick for gcc, but for kernel builds with
> > clang it results in undefined symbols:
> 
> Can't you use local different FIELD_PREP/FIELD_GET macros
> with a different name without the BUILD_BUG tests?
> 
> i.e.:
> 
> #define NFP_FIELD_PREP(_mask, _val)				\
> ({								\
> 	((typeof(_mask))(_val) << __bf_shf(_mask)) & (_mask);	\
> })
> 
> #define NFP_FIELD_GET(_mask, _reg)				\
> ({								\
> 	(typeof(_mask))(((_reg) & (_mask)) >> __bf_shf(_mask));	\
> })
> 
> Then the __always_inline can be removed from
> nfp_eth_set_bit_config too.

Thanks for the suggestion. This seems a viable alternative if David
and the NFP owners can live without the extra checking provided by
__BF_FIELD_CHECK.

  reply	other threads:[~2017-10-04 18:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 20:05 [PATCH] nfp: convert nfp_eth_set_bit_config() into a macro Matthias Kaehlcke
2017-10-03 21:50 ` Jakub Kicinski
2017-10-04 17:42   ` Matthias Kaehlcke
2017-10-04 17:44     ` David Miller
     [not found]   ` <CAAMbb05G=HBQweiWqYva_9zTnQqAcwMhJ0yYBUi26T04YA4CxQ@mail.gmail.com>
2017-10-04 18:17     ` Jakub Kicinski
2017-10-04 18:44       ` Matthias Kaehlcke
2017-10-24 16:56       ` Matthias Kaehlcke
2017-10-24 17:03         ` Jakub Kicinski
2017-10-24 17:13           ` Matthias Kaehlcke
2017-10-04 18:07 ` Joe Perches
2017-10-04 18:49   ` Matthias Kaehlcke [this message]
2017-10-04 22:22     ` Jakub Kicinski
2017-10-04 23:16       ` Matthias Kaehlcke
2017-10-04 23:25         ` Jakub Kicinski
2017-10-05  0:38           ` Manoj Gupta
2017-10-05  0:56             ` Jakub Kicinski
2017-10-05  1:50               ` Manoj Gupta
2017-10-05  2:06                 ` Jakub Kicinski
2017-10-05  2:13                   ` Manoj Gupta
2017-10-09 17:29                     ` Matthias Kaehlcke

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=20171004184957.GO173745@google.com \
    --to=mka@chromium.org \
    --cc=davem@davemloft.net \
    --cc=dianders@chromium.org \
    --cc=dirk.vandermerwe@netronome.com \
    --cc=groeck@chromium.org \
    --cc=jakub.kicinski@netronome.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manojgupta@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=renato.golin@linaro.org \
    --cc=simon.horman@netronome.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).