From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk-dev <dev@dpdk.org>,
Randy Schacher <stuart.schacher@broadcom.com>,
Peter Spreadborough <peter.spreadborough@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix build with gcc10 default fno-common
Date: Tue, 5 May 2020 10:00:04 -0700 [thread overview]
Message-ID: <CACZ4nht8dyRe4Fu6FjXUaFZwihG3dcmKYsdoCO3Xs6AijV6nHw@mail.gmail.com> (raw)
In-Reply-To: <c14f5c6a-8493-f5a2-3035-c7c8066d7909@redhat.com>
On Tue, May 5, 2020 at 7:56 AM Kevin Traynor <ktraynor@redhat.com> wrote:
> On 05/05/2020 05:03, Ajit Khaparde wrote:
> > From: Randy Schacher <stuart.schacher@broadcom.com>
> >
> > Remove the defensive compile-time checker macro.
> >
>
> Thanks Ajit/Randy. This removes the error for bnxt on my Fedora 32 system.
>
> Was chatting to David and he suggest if 'static __rte_used' could be
> added to the macro as an alternative.
>
> Checked and it [1] is working also. It seems like a cleaner fix for the
> specific issue to me. If you have an additional reason to remove the
> compile checks, it could be a separate patch or a comment added to the
> commit message.
>
> [1]
> --- a/drivers/net/bnxt/tf_core/hwrm_tf.h
> +++ b/drivers/net/bnxt/tf_core/hwrm_tf.h
> @@ -40,5 +40,5 @@ typedef enum tf_subtype {
>
> #define __BUILD_BUG_ON(condition, line) \
> - char p##line[(condition) ? 1 : -1]
> + static __rte_unused char p##line[(condition) ? 1 : -1]
>
> > Bugzilla ID: 468
> > Fixes: 8430a8b841c8 ("net/bnxt: add initial TruFlow core session open")
> > Signed-off-by: Randy Schacher <stuart.schacher@broadcom.com>
> > Reviewed-by: Peter Spreadborough <peter.spreadborough@broadcom.com>
> > Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
Patch applied to dpdk-next-net-brcm. Thanks
>
>
prev parent reply other threads:[~2020-05-05 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 4:03 Ajit Khaparde
2020-05-05 14:56 ` Kevin Traynor
2020-05-05 16:42 ` Ajit Khaparde
2020-05-05 17:00 ` Ajit Khaparde [this message]
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=CACZ4nht8dyRe4Fu6FjXUaFZwihG3dcmKYsdoCO3Xs6AijV6nHw@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=peter.spreadborough@broadcom.com \
--cc=stuart.schacher@broadcom.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).