From: Kevin Mitchell <kevmitch@arista.com>
To: aroulin@nvidia.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: neighbour netlink notifications delivered in wrong order
Date: Tue, 11 Apr 2023 12:49:19 -0700 [thread overview]
Message-ID: <ZDW5v01wOiVQSsOa@chmeee> (raw)
In-Reply-To: <1e6d685a-66c3-3443-3b35-d7b0d0753a20@nvidia.com>
-fruggeri@arista.com as he is no longer at the company
Has there been any progress in getting this patch or some other fix for this
issue into mainline. It's been working well for us so far in our testing.
next prev parent reply other threads:[~2023-04-11 19:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 23:01 neighbour netlink notifications delivered in wrong order Francesco Ruggeri
2022-06-07 2:07 ` Andy Roulin
2022-06-07 3:19 ` Stephen Hemminger
2022-06-07 16:29 ` Francesco Ruggeri
2022-06-07 17:32 ` Stephen Hemminger
2022-06-07 20:03 ` Francesco Ruggeri
2022-06-08 3:49 ` Andy Roulin
2022-06-09 16:40 ` Francesco Ruggeri
2022-06-10 16:18 ` Francesco Ruggeri
2022-06-16 18:33 ` Andy Roulin
2023-04-11 19:49 ` Kevin Mitchell [this message]
2023-04-12 0:41 ` Stephen Hemminger
2023-04-12 1:22 ` Stephen Hemminger
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=ZDW5v01wOiVQSsOa@chmeee \
--to=kevmitch@arista.com \
--cc=aroulin@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).