linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: -- END AUDIO BLOK --
Date: Fri, 11 Jul 2003 19:20:54 +0100	[thread overview]
Message-ID: <200307111820.h6BIKssN017422@hraefn.swansea.linux.org.uk> (raw)


This leaves me holding

a97_plugin_wm97xx	-	waiting final device assignment
hal2			-	For SGI. Not sure if its needed
				as there is good ALSA support
harmony			-	For PARISC. Same comment as hal2

and the config fixes which depend on the hal2/harmony decision. What
would the maintainers prefer - merge them or rely on the ALSA ones ?

It also leaves cs4281 differently broken to before. That needs a lot
more work but I'm digging into it currently

             reply	other threads:[~2003-07-11 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 18:20 Alan Cox [this message]
2003-07-11 20:06 ` -- END AUDIO BLOK -- Jeff Garzik
2003-07-14 16:10   ` audigy (was Re: -- END AUDIO BLOK --) Takashi Iwai
2003-07-14 16:04 ` -- END AUDIO BLOK -- Takashi Iwai

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=200307111820.h6BIKssN017422@hraefn.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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).