[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240306070809.05211f10@kernel.org>
Date: Wed, 6 Mar 2024 07:08:09 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Lena Wang (王娜)" <Lena.Wang@...iatek.com>
Cc: "horms@...nel.org" <horms@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "dsahern@...nel.org" <dsahern@...nel.org>,
"jiri@...nulli.us" <jiri@...nulli.us>, "Shiming Cheng (成诗明)" <Shiming.Cheng@...iatek.com>, "edumazet@...gle.com"
<edumazet@...gle.com>, "pabeni@...hat.com" <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>, "davem@...emloft.net"
<davem@...emloft.net>
Subject: Re: [PATCH net v4] ipv6: fib6_rules: flush route cache when rule is
changed
On Wed, 6 Mar 2024 07:28:39 +0000 Lena Wang (王娜) wrote:
> > The primary branch is main these days.
> > If you are using master than it may well be stale.
> >
> > For reference, the current HEAD commit is.
> >
> > 4daa873133d3 ("Merge tag 'mlx5-fixes-2024-03-01' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux")
>
> Hi Simon,
> I clone a latest netdev main branch (on the 4daa873133d3) and make a
> new patch diff. However it is totally same with PATCH v4.
>
> Could you please help to check where the stale code is?
It's not the diff, your email setup corrupted the patch.
Please try resending with git send-email ?
Powered by blists - more mailing lists