From: Lee Revell <rlrevell@joe-job.com>
To: Brian Marete <bgmarete@gmail.com>
Cc: Ricardo Cerqueira <v4l@cerqueira.org>,
Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.15-rc1
Date: Thu, 24 Nov 2005 06:32:31 -0500 [thread overview]
Message-ID: <1132831951.3473.18.camel@mindpipe> (raw)
In-Reply-To: <6dd519ae0511240209y712549bep6ba626134bb6f502@mail.gmail.com>
On Thu, 2005-11-24 at 10:09 +0000, Brian Marete wrote:
> I have not seen such an oops with Kernel 2.6.14 (Of course, I am aware
> that the -rcn kernels are for testing :) My main motivation in
> installing 2.6.15-rc5 was actually to test drive the new ALSA
> capability for saa7134 driver)
You could have done that without even rebooting, much less building a
new kernel, just download the latest ALSA from
http://www.alsa-project.org and follow the install instructions. ALSA
detects your kernel sources and patches itself to build against that
kernel. It will even work with a 2.2 kernel.
Lee
next prev parent reply other threads:[~2005-11-24 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 10:09 Oops in 2.6.15-rc1 Brian Marete
2005-11-24 11:32 ` Lee Revell [this message]
2005-11-24 16:56 ` Ricardo Cerqueira
2005-11-24 18:26 ` Dmitry Torokhov
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=1132831951.3473.18.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=bgmarete@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=v4l@cerqueira.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