From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>
Subject: ALSA bugs in kernel bugzilla
Date: Tue, 31 Jan 2006 02:43:04 -0500 [thread overview]
Message-ID: <1138693384.16102.60.camel@mindpipe> (raw)
Andrew recently sent me this list:
http://bugzilla.kernel.org/show_bug.cgi?id=5126
http://bugzilla.kernel.org/show_bug.cgi?id=5207
http://bugzilla.kernel.org/show_bug.cgi?id=5398
http://bugzilla.kernel.org/show_bug.cgi?id=5420
http://bugzilla.kernel.org/show_bug.cgi?id=5523
http://bugzilla.kernel.org/show_bug.cgi?id=5568
http://bugzilla.kernel.org/show_bug.cgi?id=5621
http://bugzilla.kernel.org/show_bug.cgi?id=5628
http://bugzilla.kernel.org/show_bug.cgi?id=5634
http://bugzilla.kernel.org/show_bug.cgi?id=5705
http://bugzilla.kernel.org/show_bug.cgi?id=5723
http://bugzilla.kernel.org/show_bug.cgi?id=5726
http://bugzilla.kernel.org/show_bug.cgi?id=5761
http://bugzilla.kernel.org/show_bug.cgi?id=5763
http://bugzilla.kernel.org/show_bug.cgi?id=5792
http://bugzilla.kernel.org/show_bug.cgi?id=5824
http://bugzilla.kernel.org/show_bug.cgi?id=5828
http://bugzilla.kernel.org/show_bug.cgi?id=5837
http://bugzilla.kernel.org/show_bug.cgi?id=5852
http://bugzilla.kernel.org/show_bug.cgi?id=5892
http://bugzilla.kernel.org/show_bug.cgi?id=5912
I check and it looks like 4-5 of these are serious. Can someone take a
look before the 1.0.11 release?
Lee
-------------------------------------------------------
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-31 7:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1138693384.16102.60.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.