From: Alex Elder <elder@ieee.org>
To: Sharath Chandra Vurukala <sharathv@codeaurora.org>,
davem@davemloft.net, kuba@kernel.org, elder@kernel.org,
cpratapa@codeaurora.org, subashab@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 15:14:23 -0500 [thread overview]
Message-ID: <ed00501e-d558-a47f-5444-b1a5a895d6db@ieee.org> (raw)
In-Reply-To: <1619121731-17782-1-git-send-email-sharathv@codeaurora.org>
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
>
> A new checksum header format is used as part of MAPv5.For RX checksum offload,
> the checksum is verified by the HW and the validity is marked in the checksum
> header of MAPv5. For TX, the required metadata is filled up so hardware can
> compute the checksum.
>
> v1->v2:
> - Fixed the compilation errors, warnings reported by kernel test robot.
> - Checksum header definition is expanded to support big, little endian
> formats as mentioned by Jakub.
>
> v2->v3:
> - Fixed compilation errors reported by kernel bot for big endian flavor.
>
> v3->v4:
> - Made changes to use masks instead of C bit-fields as suggested by Jakub/Alex.
>
> Sharath Chandra Vurukala (3):
> docs: networking: Add documentation for MAPv5
> net: ethernet: rmnet: Support for ingress MAPv5 checksum offload
> net: ethernet: rmnet: Add support for MAPv5 egress packets
>
> .../device_drivers/cellular/qualcomm/rmnet.rst | 126 +++++++++++++++--
> drivers/net/ethernet/qualcomm/rmnet/rmnet_config.h | 4 +-
> .../net/ethernet/qualcomm/rmnet/rmnet_handlers.c | 29 ++--
> drivers/net/ethernet/qualcomm/rmnet/rmnet_map.h | 11 +-
> .../net/ethernet/qualcomm/rmnet/rmnet_map_data.c | 151 ++++++++++++++++++++-
> drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c | 3 +-
> include/linux/if_rmnet.h | 27 +++-
> include/uapi/linux/if_link.h | 2 +
> 8 files changed, 318 insertions(+), 35 deletions(-)
>
next prev parent reply other threads:[~2021-04-22 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 20:02 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 ` Alex Elder [this message]
2021-04-22 23:14 ` [PATCH net-next v4 0/3] net: qualcomm: rmnet: Enable Mapv5 subashab
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=ed00501e-d558-a47f-5444-b1a5a895d6db@ieee.org \
--to=elder@ieee.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sharathv@codeaurora.org \
--cc=subashab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®