DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Wilczynski, Michal" <michal.wilczynski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH] net/ice: fix overwriting of LSE bit by DCF
Date: Fri, 18 Feb 2022 13:35:00 +0000	[thread overview]
Message-ID: <BYAPR11MB3495227967BA12596D05A43DF7379@BYAPR11MB3495.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220218115719.20471-1-michal.wilczynski@intel.com>

> -----Original Message-----
> From: Wilczynski, Michal <michal.wilczynski@intel.com>
> Sent: Friday, February 18, 2022 19:57
> To: dev@dpdk.org
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Wilczynski, Michal
> <michal.wilczynski@intel.com>
> Subject: [PATCH] net/ice: fix overwriting of LSE bit by DCF
> 
> After enabling DCF on a VF, the ice driver stops receiving
> link updates on it's Admin Receive Queue. During the init
> of DCF ice_aqc_opc_get_link_status command is send to the
> firmware without LSE(LINK STATUS EVENT) bit set. This prevents
> the ice driver from receiving up/down events, and correspondingly
> updating netdev.
> 
> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
> ---
>  drivers/net/ice/ice_dcf_parent.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Acked-by: Haiyue Wang <haiyue.wang@intel.com>

> 
> --
> 2.25.1


  reply	other threads:[~2022-02-18 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 11:57 Michal Wilczynski
2022-02-18 13:35 ` Wang, Haiyue [this message]
2022-02-20  5:04   ` Zhang, Qi Z

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=BYAPR11MB3495227967BA12596D05A43DF7379@BYAPR11MB3495.namprd11.prod.outlook.com \
    --to=haiyue.wang@intel.com \
    --cc=dev@dpdk.org \
    --cc=michal.wilczynski@intel.com \
    --cc=qi.z.zhang@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).