From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Aeolus Yang <Aeolus.Yang@atheros.com>,
David Quan <David.Quan@atheros.com>
Subject: Re: 2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34
Date: Sun, 13 Jun 2010 14:02:23 -0700 [thread overview]
Message-ID: <AANLkTimKVhaBtHujNjbiOxsgj80WF4sar2RCe-AkIU9j@mail.gmail.com> (raw)
In-Reply-To: <g77CuMUl7QI.A.5wF.V5OFMB@chimera>
For your convenience in reading the regression report here's the
802.11 and Bluetooth ones. There's one PCMCIA one which I left in as I
think these patches now go through John (?) The other ones are 1
Bluetooth regression, 1 hostap_pci, 1 iwl3945 and 1 iwlagn regression.
Luis
On Sun, Jun 13, 2010 at 7:45 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Unresolved regressions
> ----------------------
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16111
> Subject : hostap_pci: infinite registered netdevice wifi0
> Submitter : Petr Pisar <petr.pisar@atlas.cz>
> Date : 2010-06-02 20:55 (12 days old)
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16084
> Subject : iwl3945 bug in 2.6.34
> Submitter : Satish Eerpini <eerpini@gmail.com>
> Date : 2010-05-23 6:37 (22 days old)
> Message-ID : <AANLkTik_7rxDBc0TKlAfoYyM5S6Cf_Hyxbr4W5ORnTsq@mail.gmail.com>
> References : http://marc.info/?l=linux-kernel&m=127459596015626&w=2
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15862
> Subject : 2.6.34-rc4/5: iwlagn unusable until reload
> Submitter : Nico Schottelius <nico-linux-20100427@schottelius.org>
> Date : 2010-04-27 7:49 (48 days old)
> Message-ID : <20100427074934.GB3261@ikn.schottelius.org>
> References : http://marc.info/?l=linux-kernel&m=127235784004839&w=2
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15717
> Subject : bluetooth oops
> Submitter : Pavel Machek <pavel@ucw.cz>
> Date : 2010-03-14 20:14 (92 days old)
> Message-ID : <20100314201434.GE22059@elf.ucw.cz>
> References : http://marc.info/?l=linux-kernel&m=126859771528426&w=4
> Handled-By : Marcel Holtmann <marcel@holtmann.org>
> Regressions with patches
> ------------------------
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16138
> Subject : PCMCIA regression
> Submitter : Mikulas Patocka <mpatocka@redhat.com>
> Date : 2010-05-25 20:25 (20 days old)
> Message-ID : <Pine.LNX.4.64.1005251619020.12278@hs20-bc2-1.build.redhat.com>
> References : http://marc.info/?l=linux-kernel&m=127481913909672&w=2
> Handled-By : Dominik Brodowski <linux@brodo.de>
> Patch : https://bugzilla.kernel.org/attachment.cgi?id=26685
next parent reply other threads:[~2010-06-13 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <g77CuMUl7QI.A.5wF.V5OFMB@chimera>
2010-06-13 21:02 ` Luis R. Rodriguez [this message]
[not found] <g77CuMUl7QI.A.qMH.4ZpHMB@chimera>
2010-06-21 18:32 ` 2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34 Luis R. Rodriguez
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=AANLkTimKVhaBtHujNjbiOxsgj80WF4sar2RCe-AkIU9j@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=Aeolus.Yang@atheros.com \
--cc=David.Quan@atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).