From: Jakub Kicinski <kuba@kernel.org>
To: "Lena Wang (王娜)" <Lena.Wang@mediatek.com>
Cc: "horms@kernel.org" <horms@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dsahern@kernel.org" <dsahern@kernel.org>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"Shiming Cheng (成诗明)" <Shiming.Cheng@mediatek.com>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net v4] ipv6: fib6_rules: flush route cache when rule is changed
Date: Wed, 6 Mar 2024 07:08:09 -0800 [thread overview]
Message-ID: <20240306070809.05211f10@kernel.org> (raw)
In-Reply-To: <b642c63273f0dd25dbde3a48aa61903f74ac6b92.camel@mediatek.com>
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 ?
prev parent reply other threads:[~2024-03-06 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:39 [PATCH net v4] ipv6: fib6_rules: flush route cache when rule is changed Lena Wang (王娜)
2024-03-01 15:27 ` David Ahern
2024-03-01 15:28 ` Jiri Pirko
2024-03-05 4:45 ` Jakub Kicinski
2024-03-05 13:01 ` Lena Wang (王娜)
2024-03-05 15:23 ` Simon Horman
2024-03-06 7:28 ` Lena Wang (王娜)
2024-03-06 15:08 ` Jakub Kicinski [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=20240306070809.05211f10@kernel.org \
--to=kuba@kernel.org \
--cc=Lena.Wang@mediatek.com \
--cc=Shiming.Cheng@mediatek.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.