From: Johannes Berg <johannes@sipsolutions.net>
To: Bruno Randolf <br1@einfach.org>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
holgerschurig@gmail.com
Subject: Re: [PATCH 1/3] cfg80211: Add nl80211 antenna configuration
Date: Wed, 12 May 2010 10:29:54 +0200 [thread overview]
Message-ID: <1273652994.3979.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100512082325.26565.46809.stgit@tt-desk>
On Wed, 2010-05-12 at 17:23 +0900, Bruno Randolf wrote:
> + CMD(get_antenna, GET_ANTENNA);
I'm wondering ... does get_antenna really make sense as a separate
command? Seems like we could just as well report it as part of the wiphy
information dump?
johannes
next prev parent reply other threads:[~2010-05-12 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 8:23 [PATCH 0/3] antenna configuration Bruno Randolf
2010-05-12 8:23 ` [PATCH 1/3] cfg80211: Add nl80211 " Bruno Randolf
2010-05-12 8:29 ` Johannes Berg [this message]
2010-05-14 8:10 ` Bruno Randolf
2010-05-12 8:23 ` [PATCH 2/3] mac80211: Add " Bruno Randolf
2010-05-12 8:23 ` [PATCH 3/3] ath5k: Add support for " Bruno Randolf
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=1273652994.3979.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=br1@einfach.org \
--cc=holgerschurig@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.