From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Please do not pull 2.6.27-rc1 into wireless-testing
Date: Tue, 29 Jul 2008 13:46:23 -0400 [thread overview]
Message-ID: <20080729174623.GA4923@tuxdriver.com> (raw)
In-Reply-To: <488E9FB8.3080804@lwfinger.net>
On Mon, Jul 28, 2008 at 11:42:32PM -0500, Larry Finger wrote:
> As stated in the subject, please do not update wireless-testing with
> 2.6.27-rc1, at least for a while. In the thread that starts at
> http://thread.gmane.org/gmane.linux.kernel.wireless.general/18423, I
> found that commit 175f9c1bba9b825d2 breaks wireless, at least for b43.
> Until that is fixed, I think wireless-testing should remain at 2.6.26.
Have you tried the patches Johannes sent today? Do they help the
situation?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-07-30 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 4:42 Please do not pull 2.6.27-rc1 into wireless-testing Larry Finger
2008-07-29 17:46 ` John W. Linville [this message]
2008-07-30 4:47 ` David Miller
2008-07-30 5:08 ` Larry Finger
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=20080729174623.GA4923@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).