From: Paul Fertser <fercerpav@gmail.com>
To: Bruno Randolf <br1@einfach.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"Thomas d'Otreppe" <tdotreppe@gmail.com>,
Richard Farina <sidhayn@gmail.com>,
Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: [RFC][PATCH] cfg80211: report monitor interface channel via wext when possible
Date: Mon, 24 Jan 2011 10:46:59 +0300 [thread overview]
Message-ID: <20110124074659.GD25136@home.lan> (raw)
In-Reply-To: <201101241010.38393.br1@einfach.org>
On Mon, Jan 24, 2011 at 10:10:38AM +0900, Bruno Randolf wrote:
> On Sun January 23 2011 18:06:39 Johannes Berg wrote:
> > On Sat, 2011-01-22 at 03:11 +0300, Paul Fertser wrote:
> > > This makes it possible to retrieve the channel for the monitor interface
> > > in cases when it can be determined unambigously. Tested with ath5k.
> >
> > NAK.
> >
> > http://article.gmane.org/gmane.linux.kernel.wireless.general/61860
>
> > I don't think so -- I don't recall anyone ever asking before ;-)
>
> I definetly want this functionality for my WLAN monitoring tool ("horst" -
> http://br1.einfach.org/horst).
You took the quote out of the context :), Johannes meant that nobody
has asked him how exactly he would like to see this functionality
implemented, and the in the linked mail he outlines his proposal.
Johannes, i know you're a busy man (no kidding, i understand you're
doing serious work) and users should trust maintainers on their
technical decisions, but i hope you can still spare a minute to
explain me why my proposed way to use set_channel is wrong (as i'm yet
to see any drawbacks). Working with real professionals like you is a
great opportunity for me to learn and i appreciate it a lot.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
prev parent reply other threads:[~2011-01-24 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 0:11 [RFC][PATCH] cfg80211: report monitor interface channel via wext when possible Paul Fertser
2011-01-23 9:06 ` Johannes Berg
2011-01-23 9:41 ` Paul Fertser
2011-01-24 11:47 ` Johannes Berg
2011-01-24 1:10 ` Bruno Randolf
2011-01-24 7:46 ` Paul Fertser [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=20110124074659.GD25136@home.lan \
--to=fercerpav@gmail.com \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=sidhayn@gmail.com \
--cc=tdotreppe@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.