From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: "Namburu, Chandu-babu" <chandu@amd.com>,
"Modali, Bhagyada" <Bhagyada.Modali@amd.com>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v3 1/4] net/axgbe: fix scattered Rx
Date: Mon, 5 Sep 2022 17:48:18 +0100 [thread overview]
Message-ID: <61a45bd9-1484-aa02-a4cf-2040705e2f42@xilinx.com> (raw)
In-Reply-To: <MW2PR12MB2538F50A9BDF4D86A60B5B00C87F9@MW2PR12MB2538.namprd12.prod.outlook.com>
On 9/5/2022 6:00 AM, Namburu, Chandu-babu wrote:
> -----Original Message-----
> From: Modali, Bhagyada <Bhagyada.Modali@amd.com>
> Sent: Friday, September 2, 2022 2:18 PM
> To: Namburu, Chandu-babu <chandu@amd.com>; Yigit, Ferruh <Ferruh.Yigit@amd.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Modali, Bhagyada <Bhagyada.Modali@amd.com>
> Subject: [PATCH v3 1/4] net/axgbe: fix scattered Rx
>
> Error check needs to be done only for last segment of Jumbo packet.
> Freed first_seg and reset eop to 0 in error case
>
> Fixes: 965b3127d425 ("net/axgbe: support scattered Rx")
> Cc: stable@dpdk.org
>
> Signed-off-by: Bhagyada Modali <bhagyada.modali@amd.com>
>
> Acked-by: Chandubabu Namburu <chandu@amd.com>
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-09-05 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220901124948.97063-1-bhagyada.modali@amd.com>
2022-09-02 8:47 ` Bhagyada Modali
2022-09-02 8:47 ` [PATCH v3 2/4] net/axgbe: fix mbuf lengths in " Bhagyada Modali
2022-09-02 8:47 ` [PATCH v3 3/4] net/axgbe: fix length of each segment " Bhagyada Modali
2022-09-02 8:47 ` [PATCH v3 4/4] net/axgbe: fix checksum and RSS " Bhagyada Modali
2022-09-05 5:00 ` [PATCH v3 1/4] net/axgbe: fix " Namburu, Chandu-babu
2022-09-05 16:48 ` Ferruh Yigit [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=61a45bd9-1484-aa02-a4cf-2040705e2f42@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=Bhagyada.Modali@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=chandu@amd.com \
--cc=dev@dpdk.org \
--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).