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
>
> 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
From: Stefan Chulski
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 onl
On Sun, 20 Dec 2020 11:11:35 + Stefan Chulski wrote:
> > RFC patches sent for review only are obviously welcome at any time.
>
> If I post RFC patches for review only, should I add some prefix or tag for
> this?
Include RFC in the tag: [RFC net-next] or [PATCH RFC net-next],
this way patch
>
> --
> On Thu, 17 Dec 2020 18:07:58 +0200 stef...@marvell.com wrote:
> > From: Stefan Chulski
> >
> > Patch didn't fix any issue, just improve parse flow and align ipv4
> > parse flow with ipv6 parse flow.
> >
> > Currently ipv
On Thu, 17 Dec 2020 18:07:58 +0200 stef...@marvell.com wrote:
> From: Stefan Chulski
>
> 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.
> P
From: Stefan Chulski
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 onl
