From: "Luis R. Rodriguez" <mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
"Perez-Gonzalez,
Inaky"
<inaky.perez-gonzalez-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Kalle Valo <kalle.valo-X3B1VOXEql0@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] cfg80211: firmware and hardware version
Date: Thu, 1 Oct 2009 19:56:40 +0000 [thread overview]
Message-ID: <43e72e890910011256v18b30e7ck420ce80b5d35fdcb@mail.gmail.com> (raw)
In-Reply-To: <20091001170722.GC2895-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
On Thu, Oct 1, 2009 at 5:07 PM, John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> wrote:
> I don't predict a huge problem if there are
> valid extensions required for use by wireless drivers in the future.
> But for now, I'd like to see us make use of some of the debugging
> facilities available in the ethtool API -- hopefully the iwlwifi guys
> are listening... ;-)
Does the same apply to wimax then? Ethtool for 802.11 and wimax? Eh.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-01 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090924180048.14503.9579.stgit@tikku>
[not found] ` <43e72e890909241320j592e347die8a14f8bdd962ffb@mail.gmail.com>
[not found] ` <20090925044258.GA2722@tuxdriver.com>
[not found] ` <da94abde0909250947k5084db85vccafe0d3e74e2ecf@mail.gmail.com>
[not found] ` <43e72e890909250953r1714c79bsa679b96ca6f5797@mail.gmail.com>
2009-10-01 1:13 ` [PATCH 0/2] cfg80211: firmware and hardware version John W. Linville
[not found] ` <20091001011340.GA3123-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-10-01 1:19 ` [PATCH 1/3] wireless: implement basic ethtool support for cfg80211 devices John W. Linville
2009-10-01 1:19 ` [PATCH 2/3] cfg80211: add firmware and hardware version to wiphy John W. Linville
[not found] ` <1254359942-3483-2-git-send-email-linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-10-01 1:19 ` [PATCH 3/3] at76c50x-usb: set firmware and hardware version in wiphy John W. Linville
2009-10-01 1:32 ` Ben Hutchings
2009-10-01 14:27 ` Kalle Valo
2009-10-01 1:30 ` [PATCH 1/3] wireless: implement basic ethtool support for cfg80211 devices Ben Hutchings
[not found] ` <1254359942-3483-1-git-send-email-linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-10-01 8:51 ` Johannes Berg
2009-10-01 14:18 ` [PATCH 0/2] cfg80211: firmware and hardware version Kalle Valo
2009-10-01 15:18 ` John W. Linville
2009-10-01 15:33 ` Ben Hutchings
2009-10-01 16:56 ` John W. Linville
2009-10-01 16:20 ` Kalle Valo
2009-10-01 17:07 ` John W. Linville
[not found] ` <20091001170722.GC2895-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-10-01 19:56 ` Luis R. Rodriguez [this message]
2009-10-01 20:12 ` Inaky Perez-Gonzalez
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=43e72e890910011256v18b30e7ck420ce80b5d35fdcb@mail.gmail.com \
--to=mcgrof-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=inaky.perez-gonzalez-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kalle.valo-X3B1VOXEql0@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).