From: Michael Buesch <mb@bu3sch.de>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Ingo Molnar" <mingo@elte.hu>,
"Toralf Förster" <toralf.foerster@gmx.de>,
linux-acpi@vger.kernel.org, "Len Brown" <lenb@kernel.org>,
"Thierry Volpiatto" <tvolpiatt@neuf.fr>,
alsa-devel@alsa-project.org, "Jaroslav Kysela" <perex@suse.cz>,
"Takashi Iwai" <tiwai@suse.de>,
"Ben Collins" <bcollins@ubuntu.com>,
linux-wireless@vger.kernel.org,
"Maximilian Engelhardt" <maxi@daemonizer.de>,
"Gary Zambrano" <zambrano@broadcom.com>
Subject: Re: [1/3] 2.6.22-rc3: known regressions v2
Date: Fri, 1 Jun 2007 22:48:53 +0200 [thread overview]
Message-ID: <200706012248.53971.mb@bu3sch.de> (raw)
In-Reply-To: <46600F1C.5000302@googlemail.com>
On Friday 01 June 2007 14:20:44 Michal Piotrowski wrote:
> Networking
>
> Subject : b44: regression in 2.6.22
> References : http://lkml.org/lkml/2007/5/27/108
> Submitter : Maximilian Engelhardt <maxi@daemonizer.de>
> Handled-By : Michael Buesch <mb@bu3sch.de>
Well, it looks like a highres-timers problem or something
like that. So I can't really be handling that, as I have no
clue about this.
I suggest you also add Gary Zambrano <zambrano@broadcom.com>
here, as he is actually the maintainer of b44. Not me.
My role was just helping in debugging the issue, as I know
some details of b44.
> Status : problem is being debugged
--
Greetings Michael.
prev parent reply other threads:[~2007-06-01 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 12:20 [1/3] 2.6.22-rc3: known regressions v2 Michal Piotrowski
2007-06-01 20:48 ` Michael Buesch [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=200706012248.53971.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=bcollins@ubuntu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maxi@daemonizer.de \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=miklos@szeredi.hu \
--cc=mingo@elte.hu \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
--cc=toralf.foerster@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=tvolpiatt@neuf.fr \
--cc=zambrano@broadcom.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 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).