public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <stfomichev@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Stanislav Fomichev <sdf@fomichev.me>,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next 0/8] net: maintain netif vs dev prefix semantics
Date: Mon, 23 Jun 2025 14:38:06 -0700	[thread overview]
Message-ID: <aFnJPlyq-hAJTaoo@mini-arch> (raw)
In-Reply-To: <6859bbade00da_101e05294a7@willemb.c.googlers.com.notmuch>

On 06/23, Willem de Bruijn wrote:
> 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. We care only
> > about driver-visible APIs, don't touch stack-internal routines.
> > 
> > This is part 1, I'm considering following up with these (haven't looked
> > deep, maybe the ones that are frequently used are fine to keep):
> > 
> >   * dev_get_tstats64 dev_fetch_sw_netstats
> >   * dev_xdp_prog_count,
> >   * dev_add_pack dev_remove_pack dev_remove_pack
> >   * dev_get_iflink
> >   * dev_fill_forward_path
> >   * dev_getbyhwaddr_rcu dev_getbyhwaddr dev_getfirstbyhwtype
> >   * dev_valid_name dev_valid_name
> >   * dev_forward dev_forward_skb
> >   * dev_queue_xmit_nit dev_nit_active_rcu
> >   * dev_pick_tx_zero
> > 
> > Sending this out to get a sense of direction :-)
> > 
> > Stanislav Fomichev (8):
> >   net: s/dev_get_stats/netif_get_stats/
> >   net: s/dev_get_port_parent_id/netif_get_port_parent_id/
> >   net: s/dev_get_mac_address/netif_get_mac_address/
> >   net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/
> >   net: s/__dev_set_mtu/__netif_set_mtu/
> >   net: s/dev_get_flags/netif_get_flags/
> >   net: s/dev_set_threaded/netif_set_threaded/
> >   net: s/dev_close_many/netif_close_many/
> 
> Maybe also an opportunity to move the modified EXPORT_SYMBOL_GPL
> into the NETDEV_INTERNAL namespace?
> 
> Context in commit 0b7bdc7fab57 ("netdev: define NETDEV_INTERNAL")

Good idea, will go over the ones that I'm renaming to see if anything
can be reclassified as the internal, thanks!

      reply	other threads:[~2025-06-23 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 15:08 [PATCH net-next 0/8] net: maintain netif vs dev prefix semantics Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 1/8] net: s/dev_get_stats/netif_get_stats/ Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 2/8] net: s/dev_get_port_parent_id/netif_get_port_parent_id/ Stanislav Fomichev
2025-06-26 17:13   ` Willem de Bruijn
2025-06-23 15:08 ` [PATCH net-next 3/8] net: s/dev_get_mac_address/netif_get_mac_address/ Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 4/8] net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/ Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 5/8] net: s/__dev_set_mtu/__netif_set_mtu/ Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 6/8] net: s/dev_get_flags/netif_get_flags/ Stanislav Fomichev
2025-06-23 22:34   ` Stanislav Fomichev
2025-06-23 23:21     ` Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 7/8] net: s/dev_set_threaded/netif_set_threaded/ Stanislav Fomichev
2025-06-23 15:08 ` [PATCH net-next 8/8] net: s/dev_close_many/netif_close_many/ Stanislav Fomichev
2025-06-23 20:40 ` [PATCH net-next 0/8] net: maintain netif vs dev prefix semantics Willem de Bruijn
2025-06-23 21:38   ` Stanislav Fomichev [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=aFnJPlyq-hAJTaoo@mini-arch \
    --to=stfomichev@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=willemdebruijn.kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox