From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org,
linux-audio-dev@ginette.musique.umontreal.ca,
linux-m68k@lists.linux-m68k.org
Cc: Hollis R Blanchard <hollis+@andrew.cmu.edu>
Subject: Re: [UPDATE/PATCH] dmasound back-port to 2.2.18 final.
Date: Thu, 11 Jan 2001 18:06:16 +0000 [thread overview]
Message-ID: <20010111180839.E1075DB9FB@atlas.valhalla.net> (raw)
oops... there was a minor glitch in the link from the dmasound page:
(the first part of the text linked to the new version, the second to the one
I just removed ;-)
Fixed.
FWIW: I posted 2 pre-built kernels (with dmasound built-in & as a module)
and a minimalist /lib/modules/2.2.18-snd-bkport/ tgz for each.
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-11 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 18:06 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 7:28 [UPDATE/PATCH] dmasound back-port to 2.2.18 final Iain Sandoe
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=20010111180839.E1075DB9FB@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=hollis+@andrew.cmu.edu \
--cc=linux-audio-dev@ginette.musique.umontreal.ca \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).