From: "John W. Linville" <linville@tuxdriver.com>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: Chris Clayton <chris2553@googlemail.com>,
ivdoorn@gmail.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: 2.6.25-rc2 regression in rt61pci wireless driver
Date: Wed, 27 Feb 2008 12:25:46 -0500 [thread overview]
Message-ID: <20080227172546.GD3078@tuxdriver.com> (raw)
In-Reply-To: <20080227155111.GB3078@tuxdriver.com>
On Wed, Feb 27, 2008 at 10:51:11AM -0500, John W. Linville wrote:
> On Wed, Feb 27, 2008 at 08:26:42AM +0100, Stefano Brivio wrote:
> > On Tue, 26 Feb 2008 22:36:19 +0000
> > "Chris Clayton" <chris2553@googlemail.com> wrote:
> >
> > > 27 135466 rate_change 2 55
> > > 28 135717 tx_rate 2 55
> > > 29 135717 tx_status 0 0
> > > 30 135717 pf_sample 0 3584 1965 0
> > > 31 135717 rate_change 129 -541505508
> > > 32 135968 tx_rate 11 540
> >
> > Known and fixed. The fix isn't in 2.6.25-rc3 yet, though.
> >
> > Fix:
> > commit 32720eae675d08990e97bffbf71a31382599cc8a
> > Author: Stefano Brivio <stefano.brivio@polimi.it>
> > Date: Tue Jan 29 20:29:16 2008 +0100
> >
> > rc80211-pid: fix rate adjustment
>
> And it currently isn't queued for 2.6.25 at all.
>
> Chris, can you cherry-pick this from the wireless-2.6.26 tree and
> give it a test on your 2.6.25-rc3 tree? If it resolves a problem
> then I'll queue it to Dave for 2.6.25 (which will probably provoke
> a net-2.6.26 and wireless-2.6.26 rebase).
That might be easier said than done. It looks like that patch depends
on the big cfg80211 API change queued for 2.6.26.
Stefano offered to rebase that on 2.6.25. Stefano, could you post
that as part of this thread?
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-02-27 17:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 12:06 2.6.25-rc2 regression in rt61pci wireless driver Chris Clayton
2008-02-18 18:11 ` Ivo van Doorn
2008-02-18 18:16 ` Ivo van Doorn
2008-02-18 22:51 ` Chris Clayton
2008-02-19 9:26 ` Ivo van Doorn
2008-02-19 19:00 ` Chris Clayton
2008-02-19 19:46 ` Ivo van Doorn
2008-02-19 20:44 ` Chris Clayton
2008-02-19 21:03 ` Ivo van Doorn
2008-02-19 23:04 ` [Rt2400-devel] " Chris Vine
2008-02-20 16:05 ` Dan Williams
2008-02-20 20:27 ` Chris Vine
2008-02-20 20:50 ` Ivo van Doorn
2008-02-20 21:16 ` Chris Vine
2008-02-21 21:07 ` Chris Vine
2008-02-21 21:51 ` Ivo van Doorn
2008-02-21 22:46 ` Chris Vine
2008-02-21 22:51 ` Ivo van Doorn
2008-02-21 23:04 ` Chris Clayton
2008-02-21 23:20 ` Chris Vine
2008-02-22 7:39 ` Chris Clayton
2008-02-22 19:11 ` Ivo van Doorn
2008-02-22 20:33 ` Chris Vine
2008-02-20 22:13 ` Chris Clayton
2008-02-22 15:46 ` Chris Clayton
2008-02-22 19:47 ` Ivo van Doorn
2008-02-25 21:04 ` Chris Clayton
2008-02-25 22:09 ` Ivo Van Doorn
2008-02-26 19:11 ` Chris Clayton
2008-02-26 19:48 ` John W. Linville
2008-02-26 20:30 ` Ivo Van Doorn
2008-02-26 21:44 ` Stefano Brivio
2008-02-26 21:13 ` Chris Clayton
2008-02-26 21:38 ` Stefano Brivio
2008-02-26 22:36 ` Chris Clayton
2008-02-27 7:26 ` Stefano Brivio
2008-02-27 15:51 ` John W. Linville
2008-02-27 17:25 ` John W. Linville [this message]
2008-02-27 17:45 ` Chris Clayton
2008-03-02 10:33 ` Stefano Brivio
2008-03-02 15:11 ` Chris Clayton
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=20080227172546.GD3078@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=chris2553@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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).