public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "\"C.L. Tien - 田承禮\"" <cltien@cmedia.com.tw>
Cc: linux-kernel@vger.kernel.org, linux-audio-dev@music.columbia.edu,
	"收信群組-網頁 Support 信箱" <support@cmedia.com.tw>,
	"Andrew Morton" <akpm@osdl.org>,
	"Marcelo Tosatti" <marcelo@conectiva.com.br>
Subject: Re: ANN: cmpci 6.64 released
Date: Mon, 22 Mar 2004 12:53:11 -0500	[thread overview]
Message-ID: <405F2807.3000202@pobox.com> (raw)
In-Reply-To: <92C0412E07F63549B2A2F2345D3DB515F7D3EA@cm-msg-02.cmedia.com.tw>

C.L. Tien - 田承禮 wrote:
> Hi,
> 
> I made many changes for cmpci.c since last release. Changes are made as follows:
> 
> 1. Fix the S/PDIF out programming bug appeared in 6.16.
> 2. Support 8338 4-channel playback.
> 3. S/PDIF loop can be used after AC3 playback.
> 4. Legacy devices (FM, MPU401 and gameport) are served by other modules.
>    Now the code is thinner.
> 5. Remove parameters setting from kernel configure menu, they can be
>    set easily when loading the module.
> 6. Add spdif_out to output 44.1K/48K 16-bit stereo to S/PDIF out.
> 7. Add hw_copy to duplicate audio of front speakers to surround speakers.
> 8. Change code to minimum patch for kernel 2.6.

The driver looks pretty good, for both 2.4 and 2.6.  And the listed
changes above sound OK.  I see the driver is smaller now.

May I respectfully request that you submit your driver update in the
form of multiple patches, one patch per email?  This is the normal
method of submitting changes to the Linux kernel.  For example, create
and send 8 patches to Andrew Morton for inclusion in the 2.6.x kernel.
Each patch is applied after the last one, in succeeding order.  Typical
email subjects would look like

[PATCH 1/8] cmpci: fix s/pdif out
[PATCH 2/8] cmpci: support 8338 4-channel
[PATCH 3/8] cmpci: s/pdif loop
etc.

Splitting up changes in this manner allows for better verification, and
makes it easier to narrow down bugs to a specific change.  Large "one
big patch" updates often solve many bugs, and then add a few new bugs.

Best regards and thanks,

	Jeff




  reply	other threads:[~2004-03-22 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 17:24 ANN: cmpci 6.64 released C.L. Tien - 田承禮
2004-03-22 17:53 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-26  2:08 C.L. Tien - 田承禮

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=405F2807.3000202@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=cltien@cmedia.com.tw \
    --cc=linux-audio-dev@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=support@cmedia.com.tw \
    /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