From: Jakub Kicinski <kuba@kernel.org>
To: Til Kaiser <mail@tk154.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: uevent: also pass network device driver
Date: Fri, 15 Nov 2024 14:06:21 -0800 [thread overview]
Message-ID: <20241115140621.45c39269@kernel.org> (raw)
In-Reply-To: <20241115183346.597503-1-mail@tk154.de>
On Fri, 15 Nov 2024 19:33:46 +0100 Til Kaiser wrote:
> Currently, for uevent, the interface name and
> index are passed via shell variables.
>
> This commit also passes the network device
> driver as a shell variable to uevent.
Can you add more information to the commit message for the 'why'?
I'm guessing this can only be used for local one off hacks, or
can a generic (eg distro level) naming policy benefit from the driver
name?
next prev parent reply other threads:[~2024-11-15 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 18:33 [PATCH net-next] net: uevent: also pass network device driver Til Kaiser
2024-11-15 22:06 ` Jakub Kicinski [this message]
2024-11-16 16:30 ` Til Kaiser
2024-11-16 16:30 ` [PATCH net-next v2] net: sysfs: also pass network device driver to uevent Til Kaiser
2024-11-19 1:55 ` Jakub Kicinski
2024-12-05 16:28 ` Til Kaiser
2024-12-06 7:13 ` Greg KH
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=20241115140621.45c39269@kernel.org \
--to=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@tk154.de \
--cc=netdev@vger.kernel.org \
/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).