From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <petrm@nvidia.com>, <netdev@vger.kernel.org>,
<edumazet@google.com>, <horms@kernel.org>, <davem@davemloft.net>,
<pabeni@redhat.com>
Subject: Re: [net-next,5/8] net: core: neighbour: Inline neigh_update_notify() calls
Date: Mon, 19 Jan 2026 09:51:03 +0100 [thread overview]
Message-ID: <87ecnmhti1.fsf@nvidia.com> (raw)
In-Reply-To: <20260118022629.1105469-2-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> I'm a bit behind so I haven't validated this myself TBH,
> but in the interest of time perhaps you can TAL?
It looks legit. I'll send a v2.
next prev parent reply other threads:[~2026-01-19 8:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 9:54 [PATCH net-next 0/8] net: neighbour: Notify changes atomically Petr Machata
2026-01-14 9:54 ` [PATCH net-next 1/8] net: core: neighbour: Add a neigh_fill_info() helper for when lock not held Petr Machata
2026-01-16 7:22 ` Kuniyuki Iwashima
2026-01-16 12:01 ` Petr Machata
2026-01-19 12:25 ` Petr Machata
2026-01-14 9:54 ` [PATCH net-next 2/8] net: core: neighbour: Call __neigh_notify() under a lock Petr Machata
2026-01-14 9:54 ` [PATCH net-next 3/8] net: core: neighbour: Extract ARP queue processing to a helper function Petr Machata
2026-01-14 9:54 ` [PATCH net-next 4/8] net: core: neighbour: Process ARP queue later Petr Machata
2026-01-14 9:54 ` [PATCH net-next 5/8] net: core: neighbour: Inline neigh_update_notify() calls Petr Machata
2026-01-18 2:26 ` [net-next,5/8] " Jakub Kicinski
2026-01-19 8:51 ` Petr Machata [this message]
2026-01-14 9:54 ` [PATCH net-next 6/8] net: core: neighbour: Reorder netlink & internal notification Petr Machata
2026-01-14 9:54 ` [PATCH net-next 7/8] net: core: neighbour: Make one netlink notification atomically Petr Machata
2026-01-14 9:54 ` [PATCH net-next 8/8] net: core: neighbour: Make another " Petr Machata
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=87ecnmhti1.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox