> > ---------------------------------------------------------------------- > On Thu, 17 Dec 2020 18:07:58 +0200 stef...@marvell.com wrote: > > From: Stefan Chulski <stef...@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. > > > > Suggested-by: Liron Himi <lir...@marvell.com> > > Signed-off-by: Stefan Chulski <stef...@marvell.com> > > This one will need to wait until after the merge window > > -- > > # Form letter - net-next is closed > > We have already sent the networking pull request for 5.11 and therefore net- > next is closed for new drivers, features, code refactoring and optimizations. > We are currently accepting bug fixes only. > > Please repost when net-next reopens after 5.11-rc1 is cut.
OK, Thanks. > Look out for the announcement on the mailing list or check: > https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_- > 7Edavem_net- > 2Dnext.html&d=DwICAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DDQ3dKwkTIxKAl > 6_Bs7GMx4zhJArrXKN2mDMOXGh7lg&m=2CcDqbEJMvxpx15rGBe2og6oh1eZ > hVee8xvK-mjfd0E&s=r1d6bSIPQmjwJqe- > mkU_s5wyqHOU82D18G6SkVuUg5A&e= > > 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? And if all reviewers OK with change(or no comments at all), should I repost this patch again after net-next opened? Thanks, Stefan.
