From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-sound@vger.kernel.org
Subject: Re: Patch for some sound issues in Linux 2.2.8
Date: Wed, 12 May 1999 13:40:42 +0000 [thread overview]
Message-ID: <marc-linux-sound-92654246208083@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92656280921353@msgid-missing>
> All of this seems pretty obvious stuff to me. What do I have to do
> to make sure the fixes/cleanups make their way into the kernel?
Sending a diff is a good start for 2.2.x. For 2.3.x the idea is ALSA
will replace OSS.
Alan
next prev parent reply other threads:[~1999-05-12 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-12 12:40 Patch for some sound issues in Linux 2.2.8 David Luyer
1999-05-12 13:40 ` Alan Cox [this message]
1999-05-13 2:31 ` Scott Murray
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-92654246208083@msgid-missing \
--to=alan@lxorguk.ukuu.org.uk \
--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