From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: <chandu@amd.com>, Bhagyada Modali <bhagyada.modali@amd.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 1/4] net/axgbe: fix scattered Rx
Date: Thu, 1 Sep 2022 16:03:05 +0100 [thread overview]
Message-ID: <1a468c8e-a612-4191-3615-0fbd1f0b04a2@xilinx.com> (raw)
In-Reply-To: <20220901124948.97063-1-bhagyada.modali@amd.com>
On 9/1/2022 1:49 PM, Bhagyada Modali wrote:
> 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")
>
> Signed-off-by: Bhagyada Modali <bhagyada.modali@amd.com>
> ---
> v2:
> * removed the extra paranthesis
> * initialised the variables
> * updated the commit logs
Patchset looks good to me, only stable tag (Cc: stable@dpdk.org) is
missing which can be added while merging.
Will wait maintainer ack to proceed.
next prev parent reply other threads:[~2022-09-01 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 5:33 [PATCH 1/4] net/axgbe: fix scattered Rx function Bhagyada Modali
2022-09-01 5:33 ` [PATCH 2/4] " Bhagyada Modali
2022-09-01 5:33 ` [PATCH 3/4] " Bhagyada Modali
2022-09-01 5:33 ` [PATCH 4/4] " Bhagyada Modali
2022-09-01 12:49 ` [PATCH v2 1/4] net/axgbe: fix scattered Rx Bhagyada Modali
2022-09-01 12:49 ` [PATCH v2 2/4] net/axgbe: fix mbuf lengths in " Bhagyada Modali
2022-09-01 12:49 ` [PATCH v2 3/4] net/axgbe: fix length of each segment " Bhagyada Modali
2022-09-01 12:49 ` [PATCH v2 4/4] net/axgbe: fix checksum and RSS " Bhagyada Modali
2022-09-01 15:03 ` Ferruh Yigit [this message]
2022-09-02 8:47 ` [PATCH v3 1/4] net/axgbe: fix " 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
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=1a468c8e-a612-4191-3615-0fbd1f0b04a2@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=bhagyada.modali@amd.com \
--cc=chandu@amd.com \
--cc=dev@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).