From: Ari Pollak <aripollak@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.10-rc3
Date: Sat, 04 Dec 2004 14:21:10 -0500 [thread overview]
Message-ID: <cot2mv$2di$1@sea.gmane.org> (raw)
In-Reply-To: <87eki66jx8.fsf@sycorax.lbl.gov>
I looked at ALSA driver CVS a couple of days ago to see if anything has
changed since the last release (included in 2.6.10-rc1+). The only thing
significant that I found in the CVS intel8x0 driver, which added
pci_disable_device() calls, didn't seem to help the resume problem when
I applied this change to my kernel sources.
Alex Romosan wrote:
> i saw there were some changes to alsa cvs having to do with the new
> pci device handling. i'll reconfigure the kernel with alsa as modules
> and try alsa cvs to see if that makes any difference. thanks.
>
> --alex--
>
next prev parent reply other threads:[~2004-12-04 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 0:19 Linux 2.6.10-rc3 Linus Torvalds
2004-12-04 9:06 ` Soeren Sonnenburg
2004-12-04 17:06 ` Alex Romosan
2004-12-04 17:24 ` Ari Pollak
2004-12-04 17:40 ` Alex Romosan
2004-12-04 19:21 ` Ari Pollak [this message]
2004-12-04 21:17 ` Martin Josefsson
2004-12-04 21:37 ` Alex Romosan
2004-12-04 21:42 ` Martin Josefsson
2004-12-04 23:48 ` Paul Ionescu
2004-12-04 21:47 ` Giridhar Pemmasani
2004-12-04 13:35 ` Linux 2.6.10-rc3 oops when 'modprobe -r dvb-bt8xx' Eyal Lebedinsky
2004-12-05 10:15 ` Cal Peake
2004-12-05 11:51 ` Eyal Lebedinsky
2004-12-05 12:50 ` Cal Peake
2004-12-07 18:03 ` Gerd Knorr
2004-12-07 20:34 ` Michael Hunold
2004-12-07 21:55 ` Andrew Morton
2004-12-07 23:08 ` Gerd Knorr
2004-12-06 17:23 ` FS Corruption [Re: Linux 2.6.10-rc3] Kristofer T. Karas
2004-12-06 19:20 ` Linux 2.6.10-rc3 (compile stats) John Cherry
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 3:03 Linux 2.6.10-rc3 David Brownell
2004-12-05 4:07 ` Benjamin Herrenschmidt
2004-12-05 12:14 ` Russell King
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='cot2mv$2di$1@sea.gmane.org' \
--to=aripollak@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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