linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bruno Randolf <br1@einfach.org>
Cc: linville@tuxdriver.com, ath5k-devel@lists.ath5k.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/3] cfg80211: Add nl80211 antenna configuration
Date: Mon, 07 Jun 2010 11:05:14 +0200	[thread overview]
Message-ID: <1275901514.3639.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100607065858.16060.38448.stgit@tt-desk>

On Mon, 2010-06-07 at 15:58 +0900, Bruno Randolf wrote:

> + * @NL80211_CMD_GET_ANTENNA: Get antenna configuration from driver.

Since we already have runtime configuration and capability information
as part of the wiphy information printout, remind me again what was
wrong with adding antenna information there as well rather than having a
separate command to retrieve it?

As far as differentiating that information is concerned, you can easily
implement an iw "get antenna" command by just partially printing the
wiphy information, for example, no?

johannes


  parent reply	other threads:[~2010-06-07  9:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07  6:58 [PATCH v3 1/3] cfg80211: Add nl80211 antenna configuration Bruno Randolf
2010-06-07  6:59 ` [PATCH v3 2/3] mac80211: Add " Bruno Randolf
2010-06-07  6:59 ` [PATCH v3 3/3] ath5k: Add support for " Bruno Randolf
2010-06-07  9:03 ` [PATCH v3 1/3] cfg80211: Add nl80211 " Johannes Berg
2010-06-08  1:19   ` Bruno Randolf
2010-06-08  7:27     ` Johannes Berg
2010-06-07  9:05 ` Johannes Berg [this message]
2010-06-08  1:10   ` Bruno Randolf
2010-06-08  9:05     ` Johannes Berg

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=1275901514.3639.4.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=br1@einfach.org \
    --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 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).