From: Piotr Kubaj <pkubaj@anongoth.pl>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: rename a member to avoid conflict
Date: Fri, 12 Mar 2021 01:33:35 +0100 [thread overview]
Message-ID: <YEq235xS6yDkmm8p@KGPE-D16> (raw)
In-Reply-To: <20210311233033.67152-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
I may have been unclear.
This affects ppc64le overall.
The reason is that vector is a keyword on ppc64(le).
For some reason, GCC does not have an issue with it, but some future version might.
So the current issues happen when using clang (with glibc or not).
The issue that happens when attempting to build without glibc is about the lack of function to read TBR on other libc's.
This issue is resolved further in the code and does not affect bnxt.
On 21-03-11 15:30:33, Ajit Khaparde wrote:
> Address build issues with Clang and without glibc on ppc64le.
> Vector can be a keyword and should not be used in code.
> Renaming it to avoid conflict.
>
> Reported-by: Piotr Kubaj <pkubaj@FreeBSD.org>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> drivers/net/bnxt/bnxt_irq.c | 2 +-
> drivers/net/bnxt/bnxt_irq.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt_irq.c b/drivers/net/bnxt/bnxt_irq.c
> index a29ac28590..8abbadb3d1 100644
> --- a/drivers/net/bnxt/bnxt_irq.c
> +++ b/drivers/net/bnxt/bnxt_irq.c
> @@ -151,7 +151,7 @@ int bnxt_setup_int(struct bnxt *bp)
> sizeof(struct bnxt_irq), 0);
> if (bp->irq_tbl) {
> for (i = 0; i < total_vecs; i++) {
> - bp->irq_tbl[i].vector = i;
> + bp->irq_tbl[i].vector_idx = i;
> snprintf(bp->irq_tbl[i].name, len,
> "%s-%d", bp->eth_dev->device->name, i);
> bp->irq_tbl[i].handler = bnxt_int_handler;
> diff --git a/drivers/net/bnxt/bnxt_irq.h b/drivers/net/bnxt/bnxt_irq.h
> index 7b02f30973..53d9198858 100644
> --- a/drivers/net/bnxt/bnxt_irq.h
> +++ b/drivers/net/bnxt/bnxt_irq.h
> @@ -8,7 +8,7 @@
>
> struct bnxt_irq {
> rte_intr_callback_fn handler;
> - unsigned int vector;
> + unsigned int vector_idx;
> uint8_t requested;
> char name[RTE_ETH_NAME_MAX_LEN + 2];
> };
> --
> 2.21.1 (Apple Git-122.3)
>
prev parent reply other threads:[~2021-03-14 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 23:30 Ajit Khaparde
2021-03-11 23:59 ` Ajit Khaparde
2021-03-12 0:33 ` Piotr Kubaj [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=YEq235xS6yDkmm8p@KGPE-D16 \
--to=pkubaj@anongoth.pl \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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 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).