public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Zach Brown <zab@zabbo.net>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: Patch: linux-2.4.0-test11/drivers/sound/maestro.c port to new PCI interface
Date: Thu, 23 Nov 2000 01:05:44 +0000	[thread overview]
Message-ID: <20001123010543.B96@toy> (raw)
In-Reply-To: <200011220223.SAA00416@baldur.yggdrasil.com> <20001122141341.E14640@tetsuo.zabbo.net>
In-Reply-To: <20001122141341.E14640@tetsuo.zabbo.net>; from zab@zabbo.net on Wed, Nov 22, 2000 at 02:13:41PM -0500

Hi!

> > 	I also agree that the ioctl patch is kind of a bandaid over
> > the problems that you described, and, while Zach Brown can speak
> 
> The biggest problem is that the current code is gross gross gross.
> I've been avoiding dealing with it too much in the hopes that moving to
> oss_audio will make things much more friendly across the board.

What is oss_audio? I thought alsa is going in in 2.5...
								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-23 23:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  2:23 Patch: linux-2.4.0-test11/drivers/sound/maestro.c port to new PCI interface Adam J. Richter
2000-11-22 19:13 ` Zach Brown
2000-11-23  1:05   ` Pavel Machek [this message]
2000-11-23 23:10     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2000-11-22  2:25 Adam J. Richter
2000-11-21 23:02 Adam J. Richter
2000-11-21 23:35 ` Jeff Garzik
2000-11-22 18:59   ` Zach Brown

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=20001123010543.B96@toy \
    --to=pavel@suse.cz \
    --cc=adam@yggdrasil.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zab@zabbo.net \
    /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