From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>,
"Peng, ZhihongX" <zhihongx.peng@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [DPDK v2] net/i40e: add VLAN filter feature to capability
Date: Tue, 21 Jul 2020 05:01:10 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115486303A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <0e15997b-cbee-a04a-cbcb-09e437e79442@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Jeff Guo
> Sent: Tuesday, July 21, 2020 11:12 AM
> To: Peng, ZhihongX <zhihongx.peng@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [dpdk-dev] [DPDK v2] net/i40e: add VLAN filter feature to capability
>
> Acked-by: Jeff Guo <jia.guo@intel.com>
>
> On 7/21/2020 10:45 AM, zhihongx.peng@intel.com wrote:
> > From: Peng Zhihong <zhihongx.peng@intel.com>
> >
> > The rte_eth_dev_set_vlan_offload function will check vlan rx offload
> > capability, the i40e vf has vlan filter feature but
> > DEV_RX_OFFLOAD_VLAN_FILTER is not set into the capability, that will
> > cause setting fail. So need to add this capability in
> > i40e_vf_representor_dev_infos_get function.
> >
> > Fixes: e0cb96204b71 (net/i40e: add support for representor ports)
Fix line should be (".....")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Peng Zhihong <zhihongx.peng@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2020-07-21 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200720024214.13972-1-zhihongx.peng@intel.com>
2020-07-21 2:45 ` [dpdk-stable] " zhihongx.peng
2020-07-21 3:11 ` Jeff Guo
2020-07-21 5:01 ` 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=039ED4275CED7440929022BC67E706115486303A@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=stable@dpdk.org \
--cc=zhihongx.peng@intel.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).