From: subashab@codeaurora.org
To: Sharath Chandra Vurukala <sharathv@codeaurora.org>
Cc: 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 v7 0/3] net: qualcomm: rmnet: Enable Mapv5
Date: Fri, 28 May 2021 02:00:36 -0600 [thread overview]
Message-ID: <48eb11b2f69fa3b27692038c064daac8@codeaurora.org> (raw)
In-Reply-To: <1622105322-2975-1-git-send-email-sharathv@codeaurora.org>
On 2021-05-27 02:48, 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.
>
> 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.
>
> v4->v5:
> - Corrected checkpatch errors and warnings reported by patchwork.
>
> v5->v6:
> - Corrected the bug identified by Alex and incorporated all his
> comments.
>
> v6->v7:
> - Removed duplicate inclusion of linux/bitfield.h in
> rmnet_map_data.c
>
> 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 | 34 +++--
> 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 | 26 +++-
> include/uapi/linux/if_link.h | 2 +
> 8 files changed, 320 insertions(+), 37 deletions(-)
For the series-
Reviewed-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
prev parent reply other threads:[~2021-05-28 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 8:48 [PATCH net-next v7 0/3] net: qualcomm: rmnet: Enable Mapv5 Sharath Chandra Vurukala
2021-05-27 8:48 ` [PATCH net-next v7 1/3] docs: networking: Add documentation for MAPv5 Sharath Chandra Vurukala
2021-05-27 8:48 ` [PATCH net-next v7 2/3] net: ethernet: rmnet: Support for ingress MAPv5 checksum offload Sharath Chandra Vurukala
2021-05-28 22:58 ` Jakub Kicinski
2021-05-31 14:34 ` Alex Elder
2021-06-01 19:06 ` sharathv
2021-05-27 8:48 ` [PATCH net-next v7 3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets Sharath Chandra Vurukala
2021-05-28 23:11 ` Jakub Kicinski
2021-06-01 19:08 ` sharathv
2021-05-28 8:00 ` subashab [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=48eb11b2f69fa3b27692038c064daac8@codeaurora.org \
--to=subashab@codeaurora.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 \
/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).