All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Hicks, Jamey" <Jamey.Hicks@compaq.com>
Cc: Nicolas Pitre <nico@cam.org>,
	Kasparek Tomas <xkaspa06@stud.fee.vutbr.cz>,
	alsa-devel@lists.sourceforge.net,
	Linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: UDA1341TS (iPAQ H3X00) sound driver for ALSA
Date: Fri, 12 Apr 2002 18:35:46 +0100	[thread overview]
Message-ID: <a9763a$j1g$2@main.gmane.org> (raw)
In-Reply-To: <D99C1FB421989A40818B6370E31870940283ADF3@tayexc19.americas.cpqcorp.net>; from Jamey.Hicks@compaq.com on Wed, Apr 10, 2002 at 09:55:43AM -0400

On Wed, Apr 10, 2002 at 09:55:43AM -0400, Hicks, Jamey wrote:
> > -----Original Message-----
> > From: Nicolas Pitre [mailto:nico@cam.org]
> > 
> > No.  Please pick a relevant name.  H3600 is not the only 
> > device with an UDA1341 out there.
> 
> The alsa driver mentioned is iPAQ specific.  It would be useful to
> restructure it in the way the other SA11x0/UDA134x driver is structured.

I agree with Nico.  Nico is objecting to it being called *h3600* when it
is for all iPAQs, ie, H3600, H3100, H3800.

  parent reply	other threads:[~2002-04-12 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D99C1FB421989A40818B6370E31870940283ADF3@tayexc19.americas.cpqcorp.net>
2002-04-10 15:09 ` RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA Takashi Iwai
2002-04-12 17:35 ` Russell King - ARM Linux [this message]
     [not found] <D99C1FB421989A40818B6370E31870940283AE36@tayexc19.americas.cpqcorp.net>
2002-04-12 18:39 ` Kasparek Tomas
     [not found] ` <Pine.BSF.4.44.0204122027100.10809-100000@fest.stud.fee.vutbr.cz>
2002-04-12 18:56   ` Russell King - ARM Linux
2002-04-12 17:39 Hicks, Jamey
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 13:55 Hicks, Jamey
     [not found] <D99C1FB421989A40818B6370E31870940283ADF0@tayexc19.americas.cpqcorp.net>
2002-04-10 13:47 ` Nicolas Pitre
2002-04-10 13:39 Hicks, Jamey
2002-04-10 10:32 Kasparek Tomas

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='a9763a$j1g$2@main.gmane.org' \
    --to=linux@arm.linux.org.uk \
    --cc=Jamey.Hicks@compaq.com \
    --cc=Linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nico@cam.org \
    --cc=xkaspa06@stud.fee.vutbr.cz \
    /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.