From: John W. Linville <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH][3.16 MAYBE?] b43: don't warn about no 5 GHz support on 2.4 GHz devices
Date: Tue, 15 Jul 2014 15:30:11 -0400 [thread overview]
Message-ID: <20140715193011.GE26012@tuxdriver.com> (raw)
In-Reply-To: <1404846019-11079-1-git-send-email-zajec5@gmail.com>
On Tue, Jul 08, 2014 at 09:00:19PM +0200, Rafa? Mi?ecki wrote:
> This could be a bit confusing to see warning about lacking support for
> 5 GHz band if your device supports 2.4 GHz only.
>
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
> ---
> John: even I was quite confused to see this warning on my BCM5357. I
> suspected b43 incorrectly detected my WiFi as 5 GHz capable. I think
> that proposed behavior makes more sense.
> Do you think it's OK/worth to take it for 3.16?
I don't really think it merits prommotion to 3.16. I am happy to
merge it for -next.
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [PATCH][3.16 MAYBE?] b43: don't warn about no 5 GHz support on 2.4 GHz devices
Date: Tue, 15 Jul 2014 15:30:11 -0400 [thread overview]
Message-ID: <20140715193011.GE26012@tuxdriver.com> (raw)
In-Reply-To: <1404846019-11079-1-git-send-email-zajec5@gmail.com>
On Tue, Jul 08, 2014 at 09:00:19PM +0200, Rafał Miłecki wrote:
> This could be a bit confusing to see warning about lacking support for
> 5 GHz band if your device supports 2.4 GHz only.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> ---
> John: even I was quite confused to see this warning on my BCM5357. I
> suspected b43 incorrectly detected my WiFi as 5 GHz capable. I think
> that proposed behavior makes more sense.
> Do you think it's OK/worth to take it for 3.16?
I don't really think it merits prommotion to 3.16. I am happy to
merge it for -next.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-07-15 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 19:00 [PATCH][3.16 MAYBE?] b43: don't warn about no 5 GHz support on 2.4 GHz devices Rafał Miłecki
2014-07-08 19:00 ` Rafał Miłecki
2014-07-15 19:30 ` John W. Linville [this message]
2014-07-15 19:30 ` John W. Linville
2014-07-15 19:47 ` Rafał Miłecki
2014-07-15 19:47 ` Rafał Miłecki
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=20140715193011.GE26012@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@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.