From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
jv@jvosburgh.net, sdf@fomichev.me, dongchenchen2@huawei.com,
idosch@nvidia.com, n05ec@lzu.edu.cn, yuantan098@gmail.com,
nb@tipi-net.de, aleksandr.loktionov@intel.com,
dtatulea@nvidia.com
Subject: Re: [PATCH net 1/4] net: turn the rx_mode work into a generic netdev_work facility
Date: Thu, 25 Jun 2026 08:17:59 -0700 [thread overview]
Message-ID: <20260625081759.10330b7e@kernel.org> (raw)
In-Reply-To: <CAAVpQUCbT1Q9BPTLrVCjpt2vcJiWsYKa0onJ_vwnq86L73m8mw@mail.gmail.com>
On Wed, 24 Jun 2026 22:55:06 -0700 Kuniyuki Iwashima wrote:
> Oh very nice !
>
> I was drafting almost the same change for dev_set_rx_mode()
> in mcast path and some ipvlan changes.
Glad to hear! I wasn't 100% convinced by the added complexity
in the core :S
next prev parent reply other threads:[~2026-06-25 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 18:20 [PATCH net 0/4] net: avoid nested UP notifier events Jakub Kicinski
2026-06-24 18:20 ` [PATCH net 1/4] net: turn the rx_mode work into a generic netdev_work facility Jakub Kicinski
2026-06-25 5:55 ` Kuniyuki Iwashima
2026-06-25 15:17 ` Jakub Kicinski [this message]
2026-06-25 15:48 ` Stanislav Fomichev
2026-06-24 18:20 ` [PATCH net 2/4] net: add the driver-facing netdev_work scheduling API Jakub Kicinski
2026-06-25 5:55 ` Kuniyuki Iwashima
2026-06-25 15:48 ` Stanislav Fomichev
2026-06-24 18:20 ` [PATCH net 3/4] vlan: defer real device state propagation to netdev_work Jakub Kicinski
2026-06-25 5:57 ` Kuniyuki Iwashima
2026-06-25 11:37 ` Nicolai Buchwitz
2026-06-25 15:49 ` Stanislav Fomichev
2026-06-24 18:20 ` [PATCH net 4/4] selftests: bonding: add a test for VLAN propagation over a bonded real device Jakub Kicinski
2026-06-25 8:41 ` Loktionov, Aleksandr
2026-06-25 15:49 ` Stanislav Fomichev
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=20260625081759.10330b7e@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dongchenchen2@huawei.com \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jv@jvosburgh.net \
--cc=kuniyu@google.com \
--cc=n05ec@lzu.edu.cn \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=yuantan098@gmail.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.