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,
liron@marvell.com
Subject: Re: [PATCH net-next] net: mvpp2: prs: improve ipv4 parse flow
Date: Tue, 12 Jan 2021 02:00:08 +0000 [thread overview]
Message-ID: <161041680898.7943.13175555467776041590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1610289059-14962-1-git-send-email-stefanc@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sun, 10 Jan 2021 16:30:59 +0200 you wrote:
> From: Stefan Chulski <stefanc@marvell.com>
>
> Patch didn't fix any issue, just improve parse flow
> and align ipv4 parse flow with ipv6 parse flow.
>
> Currently ipv4 kenguru parser first check IP protocol(TCP/UDP)
> and then destination IP address.
> Patch introduce reverse ipv4 parse, first destination IP address parsed
> and only then IP protocol.
> This would allow extend capability for packet L4 parsing and align ipv4
> parsing flow with ipv6.
>
> [...]
Here is the summary with links:
- [net-next] net: mvpp2: prs: improve ipv4 parse flow
https://git.kernel.org/netdev/net-next/c/c73a45965dd5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-01-12 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 14:30 [PATCH net-next] net: mvpp2: prs: improve ipv4 parse flow stefanc
2021-01-12 2:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-17 16:07 stefanc
2020-12-19 18:03 ` Jakub Kicinski
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=161041680898.7943.13175555467776041590.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liron@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 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.