From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: [patch 2.6.10-rc2] oss: AC97 quirk facility
Date: Thu, 18 Nov 2004 19:41:44 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.4.53.0411181940580.8260@yvahk01.tjqt.qr> (raw)
In-Reply-To: <419CEC33.3010208@pobox.com>
>Until it's gone, the current users would prefer not-broken to broken.
Well, leave it broken and reason it with "come over to ALSA".
Jan Engelhardt
--
Gesellschaft für Wissenschaftliche Datenverarbeitung
Am Fassberg, 37077 Göttingen, www.gwdg.de
next prev parent reply other threads:[~2004-11-19 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 21:30 [patch 2.6.10-rc2] oss: AC97 quirk facility John W. Linville
2004-11-17 22:56 ` Andrew Morton
2004-11-18 1:25 ` John W. Linville
2004-11-18 18:27 ` Jeff Garzik
2004-11-18 18:36 ` Jan Engelhardt
2004-11-18 18:38 ` Jeff Garzik
2004-11-18 18:41 ` Jan Engelhardt [this message]
2004-11-18 18:45 ` Jeff Garzik
2004-11-19 1:23 ` Lee Revell
2004-11-18 18:41 ` Alan Cox
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=Pine.LNX.4.53.0411181940580.8260@yvahk01.tjqt.qr \
--to=jengelh@linux01.gwdg.de \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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).