DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Wenjun1" <wenjun1.wu@intel.com>,
	Visa Hankala <visa@hankala.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Su, Simei" <simei.su@intel.com>
Subject: RE: [PATCH] net/e1000: fix saving of stripped VLAN TCI
Date: Mon, 13 Mar 2023 07:42:07 +0000	[thread overview]
Message-ID: <DM4PR11MB59949E8DA560DE697DF1FAABD7B99@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <IA0PR11MB7955FDE231CE1FE57A2A2A64DFB99@IA0PR11MB7955.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Wu, Wenjun1 <wenjun1.wu@intel.com>
> Sent: Monday, March 13, 2023 9:39 AM
> To: Visa Hankala <visa@hankala.org>; dev@dpdk.org
> Cc: Su, Simei <simei.su@intel.com>
> Subject: RE: [PATCH] net/e1000: fix saving of stripped VLAN TCI
> 
> Hi,
> 
> > -----Original Message-----
> > From: Visa Hankala <visa@hankala.org>
> > Sent: Sunday, March 12, 2023 9:45 PM
> > To: dev@dpdk.org
> > Cc: Su, Simei <simei.su@intel.com>; Wu, Wenjun1 <wenjun1.wu@intel.com>
> > Subject: [PATCH] net/e1000: fix saving of stripped VLAN TCI
> >
> > When receiving a scattered packet, save the stripped VLAN TCI in the
> > first mbuf segment where users expect to find it.
> 
> Missing fix tag here.

Added 

Fixes: 805803445a02 ("e1000: support EM devices (also known as e1000/e1000e)")
Cc: stable@dpdk.org
> 
> >
> > Signed-off-by: Visa Hankala <visa@hankala.org>

Offline confirmed with Wenjun, Wu, agreed to add
Acked-y: Wenjun Wu <wenjun1.wu@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2023-03-13  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 13:44 Visa Hankala
2023-03-13  1:38 ` Wu, Wenjun1
2023-03-13  7:42   ` 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=DM4PR11MB59949E8DA560DE697DF1FAABD7B99@DM4PR11MB5994.namprd11.prod.outlook.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=simei.su@intel.com \
    --cc=visa@hankala.org \
    --cc=wenjun1.wu@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).