From: Christoph Hellwig <hch@infradead.org>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA update 0.9.6
Date: Mon, 28 Jul 2003 13:43:59 +0100 [thread overview]
Message-ID: <20030728134359.A2558@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0307281421360.28950-100000@pnote.perex-int.cz>; from perex@suse.cz on Mon, Jul 28, 2003 at 02:24:24PM +0200
On Mon, Jul 28, 2003 at 02:24:24PM +0200, Jaroslav Kysela wrote:
> <perex@suse.cz> (03/07/28 1.1597)
> ALSA 0.9.6 update
> - added __setup() to all midlevel modules
> - sequencer protocol 1.0.1
> - added timestamping flags for ports
> - OSS PCM emulation
> - fixed write() behaviour
> - added two new options no-silence & whole-frag
> - a try to fix OOPSes caused in the rate plugin
> - emu10k1 driver
> - more support for Audigy/Audigy2 EX
> - fixed soundfont locking
> - sb16 driver
> - fixed fm_res handling (and proc OOPS)
Any chance you could finally submit individual changes as patches /
changesets like everyone else does? For the new primary sound driver
ALSA has quite a bit too much CVS mentality, these monthly or whatever
updates make it really hard to track individual changes and you have
a rather bad track record of backing out changes done in mainline
in the meantime..
next prev parent reply other threads:[~2003-07-28 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:24 [PATCH] ALSA update 0.9.6 Jaroslav Kysela
2003-07-28 12:43 ` Christoph Hellwig [this message]
2003-07-28 13:17 ` Jaroslav Kysela
2003-07-28 13:23 ` Christoph Hellwig
2003-07-29 18:00 ` juan l.
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=20030728134359.A2558@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.