All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Kel Modderman <kel@otaku42.de>
Cc: "Kalle Valo" <kalle.valo@iki.fi>,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	"Bob Copeland" <me@bobcopeland.com>,
	"John S. Skogtvedt" <jss@bzz.no>,
	linux-wireless@vger.kernel.org
Subject: Re: Bug: 2.6.32 ath5k, unable to connect to AP on channel 13
Date: Thu, 28 Jan 2010 10:01:40 -0800	[thread overview]
Message-ID: <43e72e891001281001g5fae7bceoae57a426df13b8e0@mail.gmail.com> (raw)
In-Reply-To: <201001282327.04853.kel@otaku42.de>

On Thu, Jan 28, 2010 at 5:27 AM, Kel Modderman <kel@otaku42.de> wrote:

> Am happy for anyone else to pick up my stuff, take it change it and get a
> painless, just working, set of the software in Debian. Or even just the latter
> bit :)
>
>> Also can you recommend a kernel contact, I'd
>> like to recommend to not use CONFIG_WIRELESS_OLD_REGULATORY for a few
>> reasons [1] as it seems to be the default on the current 2.6.32
>> kernel.
>
> Debian Kernel Team <debian-kernel@lists.debian.org>, more details at:
> http://packages.qa.debian.org/l/linux-latest-2.6.html

Thanks for all your work and details, I'll go poke
debian-kernel@lists.debian.org now to see if I can help. I can try to
help with the packaging and see if there are any questions regarding
that stuff or CONFIG_WIRELESS_OLD_REGULATORY.

  Luis

  reply	other threads:[~2010-01-28 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 21:12 Bug: 2.6.32 ath5k, unable to connect to AP on channel 13 John S. Skogtvedt
2010-01-25 17:51 ` Bob Copeland
2010-01-25 18:30   ` Gábor Stefanik
2010-01-25 19:20     ` Luis R. Rodriguez
2010-01-26 10:20       ` Kalle Valo
2010-01-26 19:06         ` Luis R. Rodriguez
2010-01-28 13:27           ` Kel Modderman
2010-01-28 18:01             ` Luis R. Rodriguez [this message]
2010-01-25 19:26     ` John S. Skogtvedt
2010-01-25 19:58       ` Luis R. Rodriguez
2010-01-25 19:22   ` John S. Skogtvedt

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=43e72e891001281001g5fae7bceoae57a426df13b8e0@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=jss@bzz.no \
    --cc=kalle.valo@iki.fi \
    --cc=kel@otaku42.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=netrolller.3d@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.