Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: alsa-devel@lists.sourceforge.net,
	Karsten Wiese <annabellesgarden@yahoo.de>,
	martin-langer@gmx.de, ws@seh.de
Subject: Re: [PATCH] Tascam US-224/428 MMC Implementation
Date: Tue, 03 Aug 2004 16:33:52 +0200	[thread overview]
Message-ID: <s5hu0vkqoj3.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hd629sfjw.wl@alsa2.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

At Mon, 02 Aug 2004 17:52:35 +0200,
I wrote:
> 
> Anyway, we'll need clean up of codes before moving to alsa-kernel
> tree.  The all 2.4/2.2-specific codes should be stripped down and
> provided as patches in alsa-driver.
> 
> I can do it but I'm afraid of breaking something.  Could any usx2y
> owner take this action?

Ok, since no one gave his name, I did it :)


Now it's moved to alsa-kernel CVS tree.

Along with this action, the following items have been changed:

- the codes for old kernels are patched.  usbusx2y.c and usX2Yhwdep.c
  have the patches.

- most of snd_printd() is replaced with snd_printdd().
  CONFIG_SND_DEBUG is used commonly, and it must be annoying to print
  kernel messages at each time you start PCM.

- the complete handlers are moved to usbusx2.c from usX2Yhwdep.c
  to simplify the patches.  Instead, the initializers are exported.

- __cplusplus codes are removed from the header.

- Karsten's last patch to 0.7.2 is already merged.


I attached the patches below, so that you can test immediately before
sf's tree is synced.


Takashi

[-- Attachment #2: usx2y-kernel.dif.gz --]
[-- Type: application/octet-stream, Size: 16104 bytes --]

[-- Attachment #3: usx2y-driver.dif.gz --]
[-- Type: application/octet-stream, Size: 19776 bytes --]

      reply	other threads:[~2004-08-03 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <32814.192.168.1.8.1091390483.squirrel@192.168.1.8>
2004-08-01 20:15 ` [PATCH] Tascam US-224/428 MMC Implementation Rui Nuno Capela
2004-08-02 11:54   ` Takashi Iwai
2004-08-02 12:12     ` Rui Nuno Capela
2004-08-02 12:33       ` Takashi Iwai
2004-08-02 15:43         ` Rui Nuno Capela
2004-08-02 15:52           ` Takashi Iwai
2004-08-03 14:33             ` Takashi Iwai [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=s5hu0vkqoj3.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    --cc=martin-langer@gmx.de \
    --cc=rncbc@rncbc.org \
    --cc=ws@seh.de \
    /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