From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Arjan van de Ven <arjan@infradead.org>,
"John W. Linville" <linville@tuxdriver.com>,
torvalds@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl, rodriguez@atheros.com
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config option
Date: Tue, 28 Oct 2008 08:29:15 +0100 [thread overview]
Message-ID: <1225178955.3796.60.camel@johannes.berg> (raw)
In-Reply-To: <20081027204249.GA1620@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Mon, 2008-10-27 at 21:42 +0100, Pavel Machek wrote:
> > > it's not always nice, especially if you're trying to get rid of some
> > > nasty stuff, but think of it this way: you should be able to use a
> > > new kernel on an existing distro, at least for a reasonable type of
> > > distro (eg something shipped in, say, the last 2 years). In this case:
> > > even Fedora 10 is not likely to work!
> >
> > Well, actually, it _ought_ to work fine, with a smaller set of channels,
>
> Really? It will still break if your AP uses one of those channels, right?
Well yes, but the driver itself shouldn't simply fail as it did in
Arjan's case, it should just not find the AP rather than saying "sorry,
found error and can't continue" or something like that.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-28 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 17:30 Arjan van de Ven
2008-10-26 20:09 ` John W. Linville
2008-10-26 20:16 ` Linus Torvalds
2008-10-26 20:18 ` Arjan van de Ven
2008-10-26 20:22 ` Johannes Berg
2008-10-27 20:42 ` Pavel Machek
2008-10-28 7:29 ` Johannes Berg [this message]
2008-10-26 20:44 ` John W. Linville
2008-10-26 22:12 ` Marcel Holtmann
2008-10-28 15:13 ` 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=1225178955.3796.60.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=rodriguez@atheros.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®