From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless: Print wiphy name in sysfs.
Date: Mon, 11 Oct 2010 11:50:20 -0700 [thread overview]
Message-ID: <4CB35C6C.4060606@candelatech.com> (raw)
In-Reply-To: <1286822565.3634.83.camel@jlt3.sipsolutions.net>
On 10/11/2010 11:42 AM, Johannes Berg wrote:
> On Mon, 2010-10-11 at 11:22 -0700, Ben Greear wrote:
>
>>> basename $(readlink /sys/class/net/wlan0/phy80211)
>>
>> It looks like that could work, but it seems a lot easier to probe
>> network devices via normal manner, and then check if I can just
>> open and read /sys/class/net/[dev-name]/phy80211/name
>>
>> I can do that easily from within a C/C++ program, where as
>> doing system calls and grabbing standard output is more of
>> a pain (and more overhead).
>>
>> But, if you don't want to add my patch, it's not a big deal.
>
> I don't really mind, it just didn't seem necessary. FWIW, readlink(2) is
> also a system call that your C program could use, but if you want the
> patch instead I guess that's fine.
I think it offers a bit of use at a small cost, but certainly
it's not a critical improvement.
If the maintainer picks it up, I'll happily use it..if not,
I can carry it in my own tree or use readdir or something.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-10-11 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 17:28 [PATCH] wireless: Print wiphy name in sysfs greearb
2010-10-11 17:58 ` Johannes Berg
2010-10-11 18:04 ` Ben Greear
2010-10-11 18:10 ` Johannes Berg
2010-10-11 18:22 ` Ben Greear
2010-10-11 18:42 ` Johannes Berg
2010-10-11 18:50 ` Ben Greear [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=4CB35C6C.4060606@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).