From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Jiang, YuX" <yux.jiang@intel.com>,
"Huang, ZhiminX" <zhiminx.huang@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"ingjing.wu@intel.com" <ingjing.wu@intel.com>,
"bluca@debian.org" <bluca@debian.org>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>
Subject: RE: [PATCH v2] net/iavf: fix segmentation offload buffer size
Date: Sun, 20 Feb 2022 05:35:38 +0000 [thread overview]
Message-ID: <8b996ed6518743a1b44df21b4a42b700@intel.com> (raw)
In-Reply-To: <20220215155023.1542072-1-radu.nicolau@intel.com>
> -----Original Message-----
> From: Radu Nicolau <radu.nicolau@intel.com>
> Sent: Tuesday, February 15, 2022 11:50 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Jiang, YuX <yux.jiang@intel.com>; Huang, ZhiminX
> <zhiminx.huang@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> ingjing.wu@intel.com; bluca@debian.org; ktraynor@redhat.com; Nicolau, Radu
> <radu.nicolau@intel.com>
> Subject: [PATCH v2] net/iavf: fix segmentation offload buffer size
>
> This fix commit ff8b8bcd2ebe, which resulted in incorrect buffer size being
> computed for non IPses TSO packets.
>
> Fixes: ff8b8bcd2ebe ("net/iavf: fix segmentation offload condition")
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-02-20 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:09 [PATCH] net/iavf: fix segmentation offload buffer size Radu Nicolau
2022-02-15 6:16 ` Huang, ZhiminX
2022-02-15 7:59 ` Zhang, Qi Z
2022-02-15 10:06 ` Ferruh Yigit
2022-02-15 10:46 ` Kevin Traynor
2022-02-15 11:25 ` Ferruh Yigit
2022-02-15 10:47 ` Nicolau, Radu
2022-02-15 11:19 ` Ferruh Yigit
2022-02-15 12:30 ` Nicolau, Radu
2022-02-15 12:44 ` Ferruh Yigit
2022-02-15 12:48 ` Ferruh Yigit
2022-02-15 15:52 ` Nicolau, Radu
2022-02-15 15:50 ` [PATCH v2] " Radu Nicolau
2022-02-20 5:35 ` 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=8b996ed6518743a1b44df21b4a42b700@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ingjing.wu@intel.com \
--cc=jingjing.wu@intel.com \
--cc=ktraynor@redhat.com \
--cc=radu.nicolau@intel.com \
--cc=yux.jiang@intel.com \
--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 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.