Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Turner Arthur <justinarthur.mail@verizon.net>
To: ALSA Development <alsa-devel@alsa-project.org>
Subject: Re: Is source in CVS broken, or is it just me?
Date: Mon, 26 Jan 2004 20:56:10 -0500	[thread overview]
Message-ID: <4015C53A.9060806@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0401262010410.2959@pnote.perex-int.cz>

Jaroslav Kysela wrote:

>Use latest 2.6.2-rc kernels.
>
>	
>
Thanks for the tip, Mr. Kysela. Upon patching to the 2.6.2rcX kernel, 
and re-application of the ALSA cvs checkout, I'm up and running with a 
working ice1712 driver and no compile errors. Hot-diggity!

Thanks again,
Justin Arthur



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

      reply	other threads:[~2004-01-27  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 18:43 Is source in CVS broken, or is it just me? Justin Turner Arthur
2004-01-26 19:10 ` Jaroslav Kysela
2004-01-27  1:56   ` Justin Turner Arthur [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=4015C53A.9060806@verizon.net \
    --to=justinarthur.mail@verizon.net \
    --cc=alsa-devel@alsa-project.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