All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.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, subashab@codeaurora.org,
	stranche@codeaurora.org
Subject: Re: [PATCH net-next v8 0/3] net: qualcomm: rmnet: Enable Mapv5
Date: Wed, 02 Jun 2021 00:40:06 +0000	[thread overview]
Message-ID: <162259440606.2786.10278242816453240434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1622575716-13415-1-git-send-email-sharathv@codeaurora.org>

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



      parent reply	other threads:[~2021-06-02  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 19:28 [PATCH net-next v8 0/3] net: qualcomm: rmnet: Enable Mapv5 Sharath Chandra Vurukala
2021-06-01 19:28 ` [PATCH net-next v8 1/3] docs: networking: Add documentation for MAPv5 Sharath Chandra Vurukala
2021-06-01 19:28 ` [PATCH net-next v8 2/3] net: ethernet: rmnet: Support for ingress MAPv5 checksum offload Sharath Chandra Vurukala
2021-06-01 19:28 ` [PATCH net-next v8 3/3] net: ethernet: rmnet: Add support for MAPv5 egress packets Sharath Chandra Vurukala
2021-06-02  0:40 ` patchwork-bot+netdevbpf [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=162259440606.2786.10278242816453240434.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.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=stranche@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 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.