From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Stanislav Fomichev <sdf@fomichev.me>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 2/8] net: s/dev_get_port_parent_id/netif_get_port_parent_id/
Date: Thu, 26 Jun 2025 13:13:28 -0400 [thread overview]
Message-ID: <685d7fb87e1e6_2e676c29436@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20250623150814.3149231-3-sdf@fomichev.me>
Stanislav Fomichev wrote:
> Maintain netif vs dev semantics.
This is quite terse, when landing on this patch with a git blame.
Can you repeat the helpful intro from the cover letter, or point to or
quote the relevant paragraph in netdevices.rst?
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
next prev parent reply other threads:[~2025-06-26 17:13 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 [this message]
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
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=685d7fb87e1e6_2e676c29436@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@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