From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/iavf: fix Tx offloading flags check
Date: Mon, 30 Oct 2023 00:19:09 +0000 [thread overview]
Message-ID: <DM4PR11MB59944BCADFA4E4198E228C9BD7A1A@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8yjQg3ny_nem7_U3Js0SxYv1aXvMWqZYJNz3vLHrF0vwQ@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, October 26, 2023 4:08 PM
> To: Nicolau, Radu <radu.nicolau@intel.com>
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> dev@dpdk.org; stable@dpdk.org
> Subject: Re: [PATCH v2] net/iavf: fix Tx offloading flags check
>
> On Wed, Oct 25, 2023 at 11:13 AM Radu Nicolau <radu.nicolau@intel.com>
> wrote:
> >
> > Relax the check in the previous fix to allow packets with security
> > offload flag set.
> >
> > Fixes: 3c715591ece0 ("net/iavf: fix checksum offloading")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>
> Acked-by: David Marchand <david.marchand@redhat.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
>
>
> --
> David Marchand
prev parent reply other threads:[~2023-10-30 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 16:38 [PATCH] " Radu Nicolau
2023-10-24 5:42 ` Zhang, Qi Z
2023-10-24 8:39 ` Radu Nicolau
2023-10-24 8:44 ` David Marchand
2023-10-24 9:03 ` Radu Nicolau
2023-10-24 9:24 ` David Marchand
2023-10-25 9:12 ` [PATCH v2] " Radu Nicolau
2023-10-26 8:07 ` David Marchand
2023-10-30 0:19 ` 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=DM4PR11MB59944BCADFA4E4198E228C9BD7A1A@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
/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).