From: Stephen Hemminger <stephen@networkplumber.org>
To: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
Cc: "Hu, Jiayu" <jiayu.hu@intel.com>,
Jun Qiu <jun.qiu@jaguarmicro.com>, "dev@dpdk.org" <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] gro : fix pkt length when extra bytes are padded to ethernet frame
Date: Tue, 31 Oct 2023 11:49:54 -0700 [thread overview]
Message-ID: <20231031114954.4a1c4a9a@fedora> (raw)
In-Reply-To: <CANxNyauTU9hj=drvip0yDi9C+qxqPz92gGzm=zDj+3m5TpvG-A@mail.gmail.com>
On Mon, 17 Oct 2022 18:57:44 +0530
kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com> wrote:
> From: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
> To: "Hu, Jiayu" <jiayu.hu@intel.com>
> Cc: Jun Qiu <jun.qiu@jaguarmicro.com>, "dev@dpdk.org" <dev@dpdk.org>, David Marchand <david.marchand@redhat.com>
> Subject: Re: [PATCH] gro : fix pkt length when extra bytes are padded to ethernet frame
> Date: Mon, 17 Oct 2022 18:57:44 +0530
>
> Hi Jiayu,
>
> Please find the patch
> http://patches.dpdk.org/project/dpdk/patch/20221016144305.19249-1-kumaraparmesh92@gmail.com/
>
> I did reply with the above message ID but for some reason a new patch
> series was created. Not sure what was the mistake that I made. Should the
> commit message be the same for the series ?
>
> Thanks,
> Kumara.
I don't see a conclusive reply in this mail thread.
And the patch doesn't apply to current main.
Therefore if the problem still exists, please rebase and resubmit.
next prev parent reply other threads:[~2023-10-31 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 17:51 Kumara Parameshwaran
2022-10-10 19:32 ` David Marchand
[not found] ` <CANxNyasJ7RWk6S9hArfKc=m39huCOgab92sV4DjxDh0VENLf7Q@mail.gmail.com>
2022-10-11 5:47 ` Fwd: " kumaraparameshwaran rathinavel
2022-10-12 1:34 ` Jun Qiu
2022-10-12 7:48 ` kumaraparameshwaran rathinavel
2022-10-12 7:50 ` David Marchand
2022-10-16 7:01 ` Hu, Jiayu
2022-10-17 13:27 ` kumaraparameshwaran rathinavel
2023-10-31 18:49 ` Stephen Hemminger [this message]
2022-10-16 14:43 ` [PATCH v2] gro : check for payload length after the trim Kumara Parameshwaran
2022-10-18 8:21 ` Hu, Jiayu
2022-10-26 15:23 ` Thomas Monjalon
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=20231031114954.4a1c4a9a@fedora \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=jun.qiu@jaguarmicro.com \
--cc=kumaraparamesh92@gmail.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).