mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stefan Chulski <stefanc@marvell.com>
Cc: netdev@vger.kernel.org, thomas.petazzoni@bootlin.com,
	davem@davemloft.net, nadavh@marvell.com, ymarkman@marvell.com,
	linux-kernel@vger.kernel.org, kuba@kernel.org,
	linux@armlinux.org.uk, mw@semihalf.com, andrew@lunn.ch,
	rmk+kernel@armlinux.org.uk, atenart@kernel.org,
	lironh@marvell.com, danat@marvell.com
Subject: Re: [PATCH V2 net-next] net: mvpp2: Add parsing support for different IPv4 IHL values
Date: Fri, 16 Apr 2021 22:40:10 +0000	[thread overview]
Message-ID: <161861281091.23739.14287826762066877912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1618560917-31548-1-git-send-email-stefanc@marvell.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri, 16 Apr 2021 11:15:17 +0300 you wrote:
> From: Stefan Chulski <stefanc@marvell.com>
> 
> Add parser entries for different IPv4 IHL values.
> Each entry will set the L4 header offset according to the IPv4 IHL field.
> L3 header offset will set during the parsing of the IPv4 protocol.
> 
> Because of missed parser support for IP header length > 20, RX IPv4 checksum HW offload fails
> and skb->ip_summed set to CHECKSUM_NONE(checksum done by Network stack).
> This patch adds RX IPv4 checksum HW offload capability for frames with IP header length > 20.
> 
> [...]

Here is the summary with links:
  - [V2,net-next] net: mvpp2: Add parsing support for different IPv4 IHL values
    https://git.kernel.org/netdev/net-next/c/4ad29b1a484e

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-04-16 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  8:15 stefanc
2021-04-16 22: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=161861281091.23739.14287826762066877912.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=atenart@kernel.org \
    --cc=danat@marvell.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lironh@marvell.com \
    --cc=mw@semihalf.com \
    --cc=nadavh@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stefanc@marvell.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=ymarkman@marvell.com \
    /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®