From: Lee Revell <rlrevell@joe-job.com>
To: Nick <nick@linicks.net>
Cc: Takashi Iwai <tiwai@suse.de>,
Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: ALSA - pnp OS bios option
Date: Sat, 11 Feb 2006 17:07:32 -0500 [thread overview]
Message-ID: <1139695653.19342.130.camel@mindpipe> (raw)
In-Reply-To: <7c3341450602110556u75c4bfffq@mail.gmail.com>
On Sat, 2006-02-11 at 13:56 +0000, Nick wrote:
> Now the question - there have been a lot of alsa changes (since my
> alsa-tools was built Slack 10) - do we need to keep the alsa tools and
> stuff current too?
Yes - kernel upgrades should depend on alsa-lib upgrades (many distros
seem to get this wrong). This should be fixed in the future, but it's
been this way for some time.
Lee
next prev parent reply other threads:[~2006-02-11 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:22 ALSA - pnp OS bios option Nick Warne
2006-01-10 9:01 ` Clemens Ladisch
2006-01-10 11:27 ` [Alsa-devel] " Takashi Iwai
2006-01-10 17:59 ` Nick Warne
2006-01-10 18:12 ` Takashi Iwai
2006-02-11 10:54 ` Nick Warne
2006-02-11 13:56 ` Nick
2006-02-11 19:47 ` Lee Revell
2006-02-11 22:07 ` Lee Revell [this message]
2006-02-11 19:44 ` Lee Revell
2006-02-12 7:56 ` Nick Warne
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=1139695653.19342.130.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=tiwai@suse.de \
/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