From: subashab@codeaurora.org
To: Alex Elder <elder@ieee.org>
Cc: Sharath Chandra Vurukala <sharathv@codeaurora.org>,
davem@davemloft.net, kuba@kernel.org, elder@kernel.org,
cpratapa@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] net: qualcomm: rmnet: Enable Mapv5
Date: Thu, 22 Apr 2021 17:14:49 -0600 [thread overview]
Message-ID: <8ada4250d370acfb995cfa68b72de091@codeaurora.org> (raw)
In-Reply-To: <ed00501e-d558-a47f-5444-b1a5a895d6db@ieee.org>
On 2021-04-22 14:14, Alex Elder wrote:
> On 4/22/21 3:02 PM, Sharath Chandra Vurukala wrote:
>> This series introduces the MAPv5 packet format.
>>
>> Patch 0 documents the MAPv4/v5.
>> Patch 1 introduces the MAPv5 and the Inline checksum offload for
>> RX/Ingress.
>> Patch 2 introduces the MAPv5 and the Inline checksum offload for
>> TX/Egress.
>
> Was this supposed to be version 5?
>
> I already reviewed version 4.
>
> Please post version 5. I am going to ignore this series.
>
> -Alex
>
What are you talking about?
Patchwork shows that Sharath has posted upto v3 so far.
https://patchwork.kernel.org/project/netdevbpf/list/?submitter=197703&state=%2A&archive=both
next prev parent reply other threads:[~2021-04-22 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 20:02 [PATCH net-next v4 0/3] net: qualcomm: rmnet: Enable Mapv5 Sharath Chandra Vurukala
2021-04-22 20:02 ` [PATCH net-next v4 1/3] docs: networking: Add documentation for MAPv5 Sharath Chandra Vurukala
2021-04-23 12:32 ` Alex Elder
2021-04-22 20:02 ` [PATCH net-next v4 2/3] net: ethernet: rmnet: Support for ingress MAPv5 checksum offload Sharath Chandra Vurukala
2021-04-23 12:32 ` Alex Elder
2021-04-22 20:02 ` [PATCH net-next v4 3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets Sharath Chandra Vurukala
2021-04-23 12:32 ` Alex Elder
2021-04-22 20:14 ` [PATCH net-next v4 0/3] net: qualcomm: rmnet: Enable Mapv5 Alex Elder
2021-04-22 23:14 ` subashab [this message]
2021-04-23 0:54 ` Alex Elder
2021-04-23 12:31 ` Alex Elder
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=8ada4250d370acfb995cfa68b72de091@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sharathv@codeaurora.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 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.