All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>, "Fu, Qi" <qi.fu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: refactor DCF VLAN handling
Date: Tue, 19 Jan 2021 06:27:17 +0000	[thread overview]
Message-ID: <9d5a2e8aa72b4184a75cd5ac701d4e7e@intel.com> (raw)
In-Reply-To: <20210118113830.83593-1-haiyue.wang@intel.com>



> -----Original Message-----
> From: Wang, Haiyue <haiyue.wang@intel.com>
> Sent: Monday, January 18, 2021 7:38 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Fu, Qi <qi.fu@intel.com>; Wang, Haiyue <haiyue.wang@intel.com>
> Subject: [PATCH v2] net/ice: refactor DCF VLAN handling
> 
> Since DCF always configure the outer VLAN offloads for the target AVF, so
> rename the related variables to align with this design.
> 
> Also, the DCF needs to trace the AVF reset status to re-apply the VLAN offload
> setting, refactor the reset event handling to support this.
> 
> Change the VF representor API 'ethdev' parameter to 'vf_rep_eth_dev' to avoid
> introducing confusion with VF representor eth_dev ops name.
> 
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>]

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-01-19  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  8:24 [dpdk-dev] [PATCH v1] net/ice: refactor DCF VLAN handling Haiyue Wang
2021-01-18 11:38 ` [dpdk-dev] [PATCH v2] " Haiyue Wang
2021-01-19  6:27   ` 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=9d5a2e8aa72b4184a75cd5ac701d4e7e@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=qi.fu@intel.com \
    --cc=qiming.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.