From: Adrian Bunk <bunk@stusta.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: perex@suse.cz, alsa-devel@alsa-project.org
Subject: Re: ALSA bugs in the kernel Bugzilla
Date: Tue, 24 Jan 2006 23:26:53 +0100 [thread overview]
Message-ID: <20060124222652.GJ3590@stusta.de> (raw)
In-Reply-To: <1137810832.3241.105.camel@mindpipe>
On Fri, Jan 20, 2006 at 09:33:51PM -0500, Lee Revell wrote:
> On Sat, 2006-01-21 at 01:54 +0100, Adrian Bunk wrote:
> > The kernel Bugzilla [1] currently lists 54 open [2] ALSA bugs.
> >
> > Please review these bugs (some might as a first step require to ask the
> > submitters whether they are still present in recent kernels).
>
> I'll take a look but in the future these should go straight into the
Thanks.
> ALSA bugzilla. We do not have the resources to track the kernel
> bugzilla.
It would be good if someone could redirect bug reporters who reported
bugs in the kernel Bugzilla to the ALSA Bugzilla.
I can try to do this, but I'm no expert in differenciating e.g. whether
a problem is an ALSA problem or a PNP problem.
> Lee
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
prev parent reply other threads:[~2006-01-24 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 0:54 ALSA bugs in the kernel Bugzilla Adrian Bunk
2006-01-21 2:33 ` Lee Revell
2006-01-24 22:26 ` Adrian Bunk [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=20060124222652.GJ3590@stusta.de \
--to=bunk@stusta.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.