From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: remove unneeded experimental build flag
Date: Thu, 16 Jul 2020 16:14:19 -0700 [thread overview]
Message-ID: <CACZ4nhutE8k3EU-aW+3G_cfLasAiFAj7RFWZkP=Fx4LiFjw3ag@mail.gmail.com> (raw)
In-Reply-To: <CACZ4nhtd5GPsuQcqtE=Q2rWCLQhMAF+FRVSooS3Q3q3SSV0Vqw@mail.gmail.com>
On Thu, Jul 16, 2020 at 3:50 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:
>
> On Thu, Jul 16, 2020 at 12:26 AM David Marchand <david.marchand@redhat.com>
> wrote:
>
>> -DALLOW_EXPERIMENTAL_API is always set for in-tree compilation.
>> See https://git.dpdk.org/dpdk/commit/?id=acec04c4b2f5
>>
>> Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure")
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
Applied to dpdk-next-net-brcm. Thanks
>
>
>> ---
>> drivers/net/bnxt/Makefile | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/net/bnxt/Makefile b/drivers/net/bnxt/Makefile
>> index c54fd108d1..2c4cdd1c40 100644
>> --- a/drivers/net/bnxt/Makefile
>> +++ b/drivers/net/bnxt/Makefile
>> @@ -14,7 +14,6 @@ LIB = librte_pmd_bnxt.a
>> EXPORT_MAP := rte_pmd_bnxt_version.map
>>
>> CFLAGS += -O3
>> -CFLAGS += -DALLOW_EXPERIMENTAL_API
>> CFLAGS += $(WERROR_FLAGS)
>> LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
>> LDLIBS += -lrte_ethdev -lrte_net -lrte_kvargs
>> --
>> 2.23.0
>>
>>
prev parent reply other threads:[~2020-07-16 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 7:26 David Marchand
2020-07-16 22:50 ` Ajit Khaparde
2020-07-16 23:14 ` 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='CACZ4nhutE8k3EU-aW+3G_cfLasAiFAj7RFWZkP=Fx4LiFjw3ag@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=venkatkumar.duvvuru@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).