patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/ice: fix wrong rxdid
Date: Sun, 29 Aug 2021 11:03:44 +0000	[thread overview]
Message-ID: <6822db774e094675b0a6948fb2847e09@intel.com> (raw)
In-Reply-To: <BL3PR11MB5699CA3214B6EE89B12ADFA2FDFE9@BL3PR11MB5699.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Huang, ZhiminX <zhiminx.huang@intel.com>
> Sent: Tuesday, August 17, 2021 4:00 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: RE: [PATCH] net/ice: fix wrong rxdid
> 
> > -----Original Message-----
> > From: Zhang, Qi Z <qi.z.zhang@intel.com>
> > Sent: Tuesday, August 17, 2021 11:41 AM
> > To: Yang, Qiming <qiming.yang@intel.com>
> > Cc: Huang, ZhiminX <zhiminx.huang@intel.com>; dev@dpdk.org; Zhang, Qi
> > Z <qi.z.zhang@intel.com>; stable@dpdk.org
> > Subject: [PATCH] net/ice: fix wrong rxdid
> >
> > Since DPDK 20.11 the default rxdid is changed from 16 to 22, but the
> > DCF data path didn't change, the patch fix the gap.
> >
> > Fixes: 12443386a0b0 ("net/ice: support flex Rx descriptor RxDID22")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> > ---
> 
> Tested-by: Zhimin Huang <zhiminx.huang@intel.com >

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-08-29 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  3:41 Qi Zhang
2021-08-17  8:00 ` Huang, ZhiminX
2021-08-29 11:03   ` 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=6822db774e094675b0a6948fb2847e09@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=zhiminx.huang@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).