linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@web.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
	Bob Copeland <me@bobcopeland.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] ath9k's regulatory domain code changes (for ar9170)
Date: Tue, 24 Mar 2009 23:24:33 +0100	[thread overview]
Message-ID: <200903242324.33485.chunkeey@web.de> (raw)
In-Reply-To: <20090324205847.GB29268@tesla>

On Tuesday 24 March 2009 21:58:47 Luis R. Rodriguez wrote:
> On Tue, Mar 24, 2009 at 01:33:27PM -0700, Christian Lamparter wrote:
> > On Tuesday 24 March 2009 21:10:21 Luis R. Rodriguez wrote:
> > > On Tue, Mar 24, 2009 at 1:03 PM, Bob Copeland <me@bobcopeland.com> wrote:
> > > > On Tue, Mar 24, 2009 at 2:41 PM, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> > > > ath5k/9k specific
> > > > bits can eventually go in ath/{5k,9k} subdirs... not sure where 9170
> > > > lives then :)
> > >
> > > Wherever Christian wants it. If he finds re-usable bits then great.
> > maybe ath/9kusb ?
> 
> In that case maybe 9170/, we do have future USB plans.
alright, ath/9170/ it is!

> > > > I probably can't get to it until the weekend, but if you have more time,
> > > > Christian, feel free to adopt whatever you want from mine.  Otherwise I'll
> > > > pick up where Luis left off on the weekend.
> > Done! Patch attached, please add to the tree ;)
> 
> Nice....... so it seems all we need now is ath5k figured out and properly
> tested.
uhh, looks like ath5k/regd.c got dropped by accident?!

Regards,
	Chr

  parent reply	other threads:[~2009-03-24 22:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 18:38 [RFC] ath9k's regulatory domain code changes (for ar9170) Christian Lamparter
2009-03-24 18:59 ` Bob Copeland
2009-03-24 18:41   ` Luis R. Rodriguez
2009-03-24 20:03     ` Bob Copeland
2009-03-24 20:10       ` Luis R. Rodriguez
2009-03-24 20:31         ` Johannes Berg
2009-03-24 22:04           ` Luis R. Rodriguez
2009-03-28 16:39             ` Bob Copeland
2009-03-29 23:13               ` Nick Kossifidis
2009-03-29 23:15                 ` Nick Kossifidis
2009-03-30 12:00                   ` Bob Copeland
2009-03-24 20:33         ` Christian Lamparter
2009-03-24 20:58           ` Luis R. Rodriguez
2009-03-24 22:09             ` Bob Copeland
2009-03-24 21:14               ` Luis R. Rodriguez
2009-03-24 22:24             ` Christian Lamparter [this message]
2009-03-24 22:30               ` Bob Copeland
2009-03-24 23:13                 ` Luis R. Rodriguez
2009-03-24 23:17                   ` Luis R. Rodriguez
2009-03-24 23:52                     ` Luis R. Rodriguez
2009-03-25  1:06                       ` Bob Copeland
2009-03-25  2:30                         ` Luis R. Rodriguez
2009-03-25  2:59                           ` Luis R. Rodriguez
2009-03-25  3:15                             ` Luis R. Rodriguez
2009-03-25  3:45                               ` Luis R. Rodriguez
2009-03-29 19:39                                 ` Bob Copeland

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=200903242324.33485.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.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).