[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162259440606.2786.10278242816453240434.git-patchwork-notify@kernel.org>
Date: Wed, 02 Jun 2021 00:40:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Sharath Chandra Vurukala <sharathv@...eaurora.org>
Cc: davem@...emloft.net, kuba@...nel.org, elder@...nel.org,
cpratapa@...eaurora.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, subashab@...eaurora.org,
stranche@...eaurora.org
Subject: Re: [PATCH net-next v8 0/3] net: qualcomm: rmnet: Enable Mapv5
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Jun 2021 00:58:33 +0530 you 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.
>
> [...]
Here is the summary with links:
- [net-next,v8,1/3] docs: networking: Add documentation for MAPv5
https://git.kernel.org/netdev/net-next/c/710b797cf61b
- [net-next,v8,2/3] net: ethernet: rmnet: Support for ingress MAPv5 checksum offload
https://git.kernel.org/netdev/net-next/c/e1d9a90a9bfd
- [net-next,v8,3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets
https://git.kernel.org/netdev/net-next/c/b6e5d27e32ef
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists