netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Fomichev <stfomichev@gmail.com>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next 6/8] net: s/dev_get_flags/netif_get_flags/
Date: Mon, 23 Jun 2025 15:34:24 -0700	[thread overview]
Message-ID: <aFnWcGnwkg38q2p1@mini-arch> (raw)
In-Reply-To: <20250623150814.3149231-7-sdf@fomichev.me>

On 06/23, Stanislav Fomichev wrote:
> Maintain netif vs dev semantics.
> 
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
> ---
>  drivers/infiniband/sw/rxe/rxe_verbs.c |  2 +-
>  fs/smb/server/smb2pdu.c               |  2 +-
>  include/linux/netdevice.h             |  2 +-
>  net/8021q/vlan.c                      |  2 +-
>  net/bridge/br_netlink.c               |  2 +-
>  net/core/dev.c                        | 10 +++++-----
>  net/core/dev_ioctl.c                  |  2 +-
>  net/core/rtnetlink.c                  |  4 ++--
>  net/ipv4/fib_frontend.c               |  2 +-
>  net/ipv4/fib_semantics.c              |  2 +-
>  net/ipv4/nexthop.c                    |  2 +-
>  net/ipv6/addrconf.c                   |  2 +-
>  net/mpls/af_mpls.c                    |  6 +++---
>  net/wireless/wext-core.c              |  2 +-
>  14 files changed, 21 insertions(+), 21 deletions(-)

Looks like I missed something in vlan_device_event:

net/8021q/vlan.c: In function ‘vlan_device_event’:
net/8021q/vlan.c:507:24: error: implicit declaration of function ‘dev_get_flags’; did you mean ‘dev_get_alias’? [-Werror=implicit-function-declaration]
  507 |                 flgs = dev_get_flags(dev);
      |                        ^~~~~~~~~~~~~
      |                        dev_get_alias

---
pw-bot: cr

  reply	other threads:[~2025-06-23 22:34 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 [this message]
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

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=aFnWcGnwkg38q2p1@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 \
    /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).