Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: perex@suse.cz
Cc: alsa-devel@alsa-project.org
Subject: ALSA bugs in the kernel Bugzilla
Date: Sat, 21 Jan 2006 01:54:32 +0100	[thread overview]
Message-ID: <20060121005432.GN31803@stusta.de> (raw)

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).

For both these bugs and future bugs in the kernel Bugzilla, it would be 
good if someone would volunteer to review ALSA bugs in the kernel 
Bugzilla, and if they are actually bugs in ALSA (and not bugs in 
ACPI/PNP/... affecting ALSA drivers) ask the submitters to also file a 
bug in the ALSA bug tracking system leaving a pointer to the URL in the 
ALSA bug tracking system in the kernel Bugzilla.

TIA
Adrian

[1] http://bugzilla.kernel.org/
[2] Status NEW/ASSIGNED/VERIFIED/DEFERRED/NEEDINFO

-- 

       "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

             reply	other threads:[~2006-01-21  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  0:54 Adrian Bunk [this message]
2006-01-21  2:33 ` ALSA bugs in the kernel Bugzilla Lee Revell
2006-01-24 22:26   ` Adrian Bunk

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=20060121005432.GN31803@stusta.de \
    --to=bunk@stusta.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    /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