From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
David Harton <dharton@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/i40e: Eliminate weak symbols in i40e_rxtx.c
Date: Wed, 29 May 2019 17:18:49 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153391CE0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20190517102127.GA660@bricha3-MOBL.ger.corp.intel.com>
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Friday, May 17, 2019 3:21 AM
> To: David Harton <dharton@cisco.com>
> Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: Re: [PATCH v3] net/i40e: Eliminate weak symbols in i40e_rxtx.c
>
> On Thu, May 16, 2019 at 02:28:03PM -0400, David Harton wrote:
> > Use of weak symbols can hide makefile errors especially when custom
> > makefiles are used. Removing the use of weak symbols to avoid a stub
> > function being linked in production code.
> >
> > Signed-off-by: David Harton <dharton@cisco.com>
> > ---
> >
> > v3 - added CONFIG_RTE_LIBRTE_I40E_INC_VECTOR to makefile
> > v2 - added CC_AVX2_SUPPORT check to code enabling avx2 vectors
> >
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2019-05-29 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 13:05 [dpdk-dev] [PATCH] " David Harton
2019-05-15 13:05 ` David Harton
2019-05-15 14:13 ` Bruce Richardson
2019-05-15 14:13 ` Bruce Richardson
2019-05-15 16:13 ` [dpdk-dev] [PATCH v2] " David Harton
2019-05-15 16:13 ` David Harton
2019-05-16 14:08 ` Bruce Richardson
2019-06-04 15:59 ` Ferruh Yigit
2019-06-04 16:19 ` David Harton (dharton)
2019-06-06 9:07 ` Ferruh Yigit
2019-06-04 16:25 ` Bruce Richardson
2019-05-16 18:28 ` [dpdk-dev] [PATCH v3] " David Harton
2019-05-17 10:21 ` Bruce Richardson
2019-05-29 17:18 ` Zhang, Qi Z [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=039ED4275CED7440929022BC67E7061153391CE0@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.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).