From: David Miller <davem@davemloft.net>
To: dh.herrmann@gmail.com
Cc: netdev@vger.kernel.org, teg@jklm.no, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] Provide netdev naming-policy via sysfs
Date: Fri, 28 Mar 2014 14:54:10 -0400 (EDT) [thread overview]
Message-ID: <20140328.145410.1817326821928803131.davem@davemloft.net> (raw)
In-Reply-To: <1395839117-20090-1-git-send-email-dh.herrmann@gmail.com>
From: David Herrmann <dh.herrmann@gmail.com>
Date: Wed, 26 Mar 2014 14:05:13 +0100
> The main use-case is to allow udev to skip applying reliable ifnames to virtual
> devices. For instance, if wifi-P2P devices are created, wpas already provides a
> suitable naming-policy and udev shouldn't touch these devices. Same is true for
> other virtual devices.
This makes no sense at all.
If udev should avoid applying names to wifi-P2P devices, that policy can
be instituted completely inside of udev. There is no need whatsoever
for kernel support.
udev can look at the device type, and policies can be defined that key
off of that device type, entirely in userspace.
I'm not applying this patch series, sorry.
next prev parent reply other threads:[~2014-03-28 18:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 13:05 David Herrmann
2014-03-26 13:05 ` [PATCH v5 1/4] net: add name_assign_type netdev attribute David Herrmann
2014-03-26 13:05 ` [PATCH v5 2/4] mac80211: set NET_NAME_USER for user-space created ifs David Herrmann
2014-03-26 13:05 ` [PATCH v5 3/4] ath6kl: set NET_NAME_USER for P2P ifs David Herrmann
2014-03-26 13:05 ` [PATCH v5 4/4] brcmfmac: " David Herrmann
2014-03-28 18:54 ` David Miller [this message]
2014-03-28 19:34 ` [PATCH v5 0/4] Provide netdev naming-policy via sysfs David Herrmann
2014-03-28 21:02 ` David Miller
2014-03-28 20:51 ` Tom Gundersen
2014-03-28 21:21 ` David Miller
2014-03-28 22:39 ` Tom Gundersen
2014-03-29 1:42 ` David Miller
2014-03-29 9:46 ` Tom Gundersen
2014-03-29 19:37 ` David Miller
2014-03-29 19:48 ` Kay Sievers
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=20140328.145410.1817326821928803131.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dh.herrmann@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=teg@jklm.no \
/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
all inboxes | Powered by JetHome®