linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "Bing Zhao" <bzhao@marvell.com>,
	"linux-netdev@vger.kernel.org" <linux-netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Paul Stewart" <pstew@chromium.org>
Subject: Re: [PATCH] net-sysfs: Add entry for nl80211 interface type
Date: Thu, 18 Apr 2013 21:18:57 +0200	[thread overview]
Message-ID: <51704721.2020001@broadcom.com> (raw)
In-Reply-To: <CD07F4FD-7136-44EA-A39C-5AB660726BDE@holtmann.org>

On 04/18/2013 09:10 PM, Marcel Holtmann wrote:
> Hi Bing,
>
>>>> Add a "wireless/nl80211_iftype" entry in the net device sysfs
>>>> file structure to indicate the mode of the wireless device so
>>>> it can be discovered easily from userspace.
>>>
>>> I do question a little bit the usefulness for this one.
>>> It would only work on netdev and on wdev devices.
>>
>> It's true. That's why the new sysfs entry is added in the 'wireless' placeholder.
>>
>> /sys/class/net/ethX/wireless/
>>
>> For non-wireless dev, this won't apply.
>
> I have to correct myself. I meant it does NOT work for wdev. Please just go with nl80211 for this kind of information. It is the right way to handle it. Not some sysfs file.
>

I wanted to correct you on P2P but that would be diverging from the real 
message. Totally agreeing. Why add another user-space API when the 
nl80211 API can provide the information.

Gr. AvS



      reply	other threads:[~2013-04-18 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 22:06 [PATCH] net-sysfs: Add entry for nl80211 interface type Bing Zhao
2013-04-17 22:09 ` Johannes Berg
2013-04-18  6:14   ` Nicolas Cavallari
2013-04-18  6:43     ` Marcel Holtmann
2013-04-18  7:03       ` Paul Stewart
2013-04-18 15:46         ` Marcel Holtmann
     [not found]   ` <CAMcMvsjh4y=84hM+dCcFvb1xxSq5c3HqTBg6VyaCZkh5s=E5yA@mail.gmail.com>
2013-04-22 13:29     ` Johannes Berg
2013-04-22 13:55       ` Paul Stewart
2013-04-17 22:54 ` Marcel Holtmann
2013-04-18 19:03   ` Bing Zhao
2013-04-18 19:10     ` Marcel Holtmann
2013-04-18 19:18       ` Arend van Spriel [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=51704721.2020001@broadcom.com \
    --to=arend@broadcom.com \
    --cc=bzhao@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-netdev@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=pstew@chromium.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).