From: "Lawrence Lee" <lfqlee314@gmail.com>
To: "Ido Schimmel" <idosch@nvidia.com>
Cc: "David Ahern" <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>, <netdev@vger.kernel.org>,
"Arun Ajith S" <aajith@arista.com>,
"Roopa Prabhu" <roopa@nvidia.com>,
"Jaehee Park" <jhpark1013@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Shuah Khan" <shuah@kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v4 2/2] selftests: net: test untracked NA recovery of FAILED neighbors
Date: Wed, 23 Sep 2026 17:49:33 +0000 [thread overview]
Message-ID: <DLMVW6Z8IU9P.31OHF60Q6YCWP@gmail.com> (raw)
In-Reply-To: <20260923083633.GA2626135@shredder>
On Wed Sep 23, 2026 at 8:36 AM UTC, Ido Schimmel wrote:
> You shouldn't have added a Fixes tag. Backporting this patch to older
> kernels will make the test fail. Wait for feedback from Jakub / Paolo
> before posting v5. They might agree to strip it before applying.
>
That's my mistake, I added it in response to Sashiko review feedback on
v3 but thought it was just for documentation purposes, I didn't realize
the tag would cause it to get backported since I only submitted to
net-next. Sorry about that, will wait to hear from Jakub/Paolo before
sending any new versions.
prev parent reply other threads:[~2026-09-23 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 1:34 [PATCH net-next v4 0/2] ipv6: update NUD_FAILED neighbors from NA messages Lawrence Lee
2026-09-23 1:34 ` [PATCH net-next v4 1/2] " Lawrence Lee
2026-09-23 1:34 ` [PATCH net-next v4 2/2] selftests: net: test untracked NA recovery of FAILED neighbors Lawrence Lee
2026-09-23 8:36 ` Ido Schimmel
2026-09-23 17:49 ` Lawrence Lee [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=DLMVW6Z8IU9P.31OHF60Q6YCWP@gmail.com \
--to=lfqlee314@gmail.com \
--cc=aajith@arista.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jhpark1013@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=roopa@nvidia.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®