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 v2 0/3] net: qualcomm: rmnet: Enable Mapv5
Date: Mon, 22 Feb 2021 10:35:01 -0700 [thread overview]
Message-ID: <1a93bc111339e4d3c4e4b765945ab150@codeaurora.org> (raw)
In-Reply-To: <1614012946-23506-1-git-send-email-sharathv@codeaurora.org>
On 2021-02-22 09:55, Sharath Chandra Vurukala wrote:
> This series introduces the MAPv5 packet format.
>
> Patch 0 documents the MAPv5.
> Patch 1 introduces the Mapv5 and the Inline checksum offload for RX.
> Patch 2 introduces the Mapv5 and the Inline checksum offload for TX.
>
> 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.
>
> Sharath Chandra Vurukala (3):
> docs: networking: Add documentation for MAPv5
> net: ethernet: rmnet: Support for downlink MAPv5 checksum offload
> net: ethernet: rmnet: Add support for Mapv5 uplink packet
>
> .../device_drivers/cellular/qualcomm/rmnet.rst | 53 ++++++-
> 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 | 22 ++-
> .../net/ethernet/qualcomm/rmnet/rmnet_map_data.c | 153
> ++++++++++++++++++++-
> include/linux/if_rmnet.h | 24 +++-
> include/uapi/linux/if_link.h | 2 +
> 7 files changed, 263 insertions(+), 29 deletions(-)
For the series-
Reviewed-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
prev parent reply other threads:[~2021-02-22 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:55 [PATCH net-next v2 0/3] net: qualcomm: rmnet: Enable Mapv5 Sharath Chandra Vurukala
2021-02-22 16:55 ` [PATCH net-next v2 1/3] docs: networking: Add documentation for MAPv5 Sharath Chandra Vurukala
2021-02-22 16:55 ` [PATCH net-next v2 2/3] net: ethernet: rmnet: Support for downlink MAPv5 checksum offload Sharath Chandra Vurukala
2021-02-22 17:55 ` Alex Elder
2021-02-22 19:49 ` kernel test robot
2021-02-23 10:52 ` Geert Uytterhoeven
2021-02-22 16:55 ` [PATCH net-next v2 3/3] net: ethernet: rmnet: Add support for Mapv5 uplink packet Sharath Chandra Vurukala
2021-02-22 17:35 ` 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=1a93bc111339e4d3c4e4b765945ab150@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).