From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: sedat.dilek@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>,
Nick Kossifidis <mickflemm@gmail.com>,
Nicolas Stransky <Nico@stransky.cx>,
sgh@sgh.dk, John Linville <linville@tuxdriver.com>
Subject: Re: 2.6.38-rc4-git5: Reported regressions from 2.6.37
Date: Mon, 14 Feb 2011 00:45:05 +0100 [thread overview]
Message-ID: <201102140045.05455.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTinQnH7YEeuHj3zAZo1RReXSxcQqUxTw1ocTp4R2@mail.gmail.com>
On Sunday, February 13, 2011, Sedat Dilek wrote:
> On Sun, Feb 13, 2011 at 12:07 PM, Sedat Dilek
> <sedat.dilek@googlemail.com> wrote:
> > On Sat, Feb 12, 2011 at 11:57 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> This message contains a list of some regressions from 2.6.37,
> >> for which there are no fixes in the mainline known to the tracking team.
> >> If any of them have been fixed already, please let us know.
> >>
> >> If you know of any other unresolved regressions from 2.6.37, please let us
> >> know either and we'll add them to the list. Also, please let us know
> >> if any of the entries below are invalid.
> >>
> >> Each entry from the list will be sent additionally in an automatic reply
> >> to this message with CCs to the people involved in reporting and handling
> >> the issue.
> >>
> >>
> >> Listed regressions statistics:
> >>
> >> Date Total Pending Unresolved
> >> ----------------------------------------
> >> 2011-02-12 39 20 18
> >> 2011-02-03 19 11 7
> >>
> >>
> >> Unresolved regressions
> >> ----------------------
> >
> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27382
> >> Subject : ath5k phy0: gain calibration timeout
> >> Submitter : Nicolas Stransky <Nico@stransky.cx>
> >> Date : 2011-01-23 00:18 (21 days old)
> >>
> >
> > As I looked into the BR #27382...
> > The patch by Nick Kossifidis from comment #32 (see [1] and [2]) fixed
> > the problem for two affected users.
> >
> > As I have an ath5k wifi device (but I am not affected) on one of my
> > machines, I could test also.
> >
> > Hey, Nick :-)
> > You promised to send a fix to linux-wireless ML (hope, I didn't oversee it).
> >
> > Raphael, might be good to wait for the promised patch?
> >
> > - Sedat -
> >
> > [1] https://bugzilla.kernel.org/show_bug.cgi?id=27382#c32
> > [2] http://www.kernel.org/pub/linux/kernel/people/mickflemm/fastchanfix.patch
> >
>
> Oops, shame on me... Nick's patch was already sent to l-w ML.
>
> See "[PATCH] ath5k: Fix fast channel switching" [1].
>
> Raphael, can you add the reference to the patch to the entry/list?
> Thanks.
>
> The patch is already in linux-next [2], but I am not sure if it is in
> Linus-tree, already.
>
> - Sedat -
>
> [1] https://patchwork.kernel.org/patch/530811/
> [2] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=c210de8f88215db31cf3529c9763fc3124d6e09d
Updated status information, thanks.
Rafael
prev parent reply other threads:[~2011-02-13 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 22:57 2.6.38-rc4-git5: Reported regressions from 2.6.37 Rafael J. Wysocki
2011-02-13 10:50 ` Sedat Dilek
2011-02-13 11:02 ` Rafael J. Wysocki
2011-02-13 11:07 ` Sedat Dilek
2011-02-13 11:21 ` Sedat Dilek
2011-02-13 23:45 ` Rafael J. Wysocki [this message]
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=201102140045.05455.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Nico@stransky.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.com \
--cc=sedat.dilek@gmail.com \
--cc=sgh@sgh.dk \
/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).