Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linux-sound@vger.kernel.org
Subject: Re: [PATCH] 2.4.18 linux/drivers/maestro.c dev_audio flaw
Date: Mon, 01 Jul 2002 16:15:22 +0000	[thread overview]
Message-ID: <marc-linux-sound-102554037208993@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-102550820111554@msgid-missing>

Zach Brown wrote:
>>It seems that the value of ess->dev_audio is wrongly interpreted. 
> 
> 
> Thanks for attacking this driver, Samuel.  Your patches have looked good
> so far.  I'm sorry I'm not more involved; its been quite a while since
> I've futzed about with the maestro(s).



I'm afraid I missed the original patches :(

But I am willing to review and apply drivers/sound [sound/oss in 2.5] 
patches, if no one else (Alan?) does so.

Regards,

	Jeff




      parent reply	other threads:[~2002-07-01 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-30 21:49 [PATCH] 2.4.18 linux/drivers/maestro.c dev_audio flaw Samuel Thibault
2002-07-01 16:07 ` Zach Brown
2002-07-01 16:15 ` Jeff Garzik [this message]

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=marc-linux-sound-102554037208993@msgid-missing \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-sound@vger.kernel.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