The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Bruno Randolf <br1@einfach.org>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
	Derek Smithies <derek@indranet.co.nz>,
	"bob@bobcopeland.com" <bob@bobcopeland.com>,
	"ath5k-devel@lists.ath5k.org" <ath5k-devel@venema.h4ckr.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	<johannes@sipsolutions.net>, <linville@tuxdriver.com>,
	<nbd@openwrt.org>, <linux-kernel@vger.kernel.org>,
	Joel Becker <joel.becker@oracle.com>, <greg@kroah.com>
Subject: Re: [ath5k-devel] [PATCH 00/10] ANI for ath5k
Date: Thu, 25 Mar 2010 18:06:34 -0700	[thread overview]
Message-ID: <20100326010634.GB2385@tux> (raw)
In-Reply-To: <201003260953.49021.br1@einfach.org>

Adding a few more people for wider review on this.

On Thu, Mar 25, 2010 at 05:53:48PM -0700, Bruno Randolf wrote:
> On Friday 26 March 2010 09:44:31 Luis R. Rodriguez wrote:
> > > as well, we all agree that there should be userland controls. the
> > > questions is just about the interface to use.
> > 
> > ANI is specific to Atheros cards so debugfs would do it. If we want to
> > have a more rigit API we could use a configfs entry for ath9k.
> 
> debugfs definetly is the wrong place! users might compile the module with 
> debugging disabled (for performance reasons, e.g.).
> 
> are you sure about configfs? as far as i read about it it's for the dynamic 
> creation of kernel objects, which is not what we are doing here. or did the 
> rules change in the mean time?

I intended on writing a file system API for 802.11 management a while
ago through configfs, the only reason why I put it aside is our focus
was to get a netlink based API done. I think its reasonable to use
it for configuration of specific devices parameters though given that
we don't have a private API through nl80211.

  Luis

           reply	other threads:[~2010-03-26  1:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201003260953.49021.br1@einfach.org>]

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=20100326010634.GB2385@tux \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=bob@bobcopeland.com \
    --cc=br1@einfach.org \
    --cc=derek@indranet.co.nz \
    --cc=greg@kroah.com \
    --cc=joel.becker@oracle.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.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