From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v4 6/7] net: s/dev_set_threaded/netif_set_threaded/
Date: Tue, 15 Jul 2025 16:36:47 -0700 [thread overview]
Message-ID: <20250715163647.0c25d113@kernel.org> (raw)
In-Reply-To: <20250714221855.3795752-7-sdf@fomichev.me>
On Mon, 14 Jul 2025 15:18:54 -0700 Stanislav Fomichev wrote:
> Commit cc34acd577f1 ("docs: net: document new locking reality")
> introduced netif_ vs dev_ function semantics: the former expects locked
> netdev, the latter takes care of the locking. We don't strictly
> follow this semantics on either side, but there are more dev_xxx handlers
> now that don't fit. Rename them to netif_xxx where appropriate.
>
> Note that one dev_set_threaded call still remains in mt76 for debugfs file.
I applied Sami's patch yesterday, this needs a respin, sorry.
--
pw-bot: cr
next prev parent reply other threads:[~2025-07-15 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 22:18 [PATCH net-next v4 0/7] net: maintain netif vs dev prefix semantics Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 1/7] net: s/dev_get_port_parent_id/netif_get_port_parent_id/ Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 2/7] net: s/dev_get_mac_address/netif_get_mac_address/ Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 3/7] net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/ Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 4/7] net: s/__dev_set_mtu/__netif_set_mtu/ Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 5/7] net: s/dev_get_flags/netif_get_flags/ Stanislav Fomichev
2025-07-14 22:18 ` [PATCH net-next v4 6/7] net: s/dev_set_threaded/netif_set_threaded/ Stanislav Fomichev
2025-07-15 23:36 ` Jakub Kicinski [this message]
2025-07-14 22:18 ` [PATCH net-next v4 7/7] net: s/dev_close_many/netif_close_many/ 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=20250715163647.0c25d113@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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.