From: Clemens Ladisch <clemens@ladisch.de>
To: David Helstroom <helstroom@google.com>
Cc: perex@perex.cz, tiwai@suse.de, eldad@fogrefinery.com,
damien@zamaudio.com, pete.leigh@gmail.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] Add a USB audio quirk for the NuForce UDH-100 device.
Date: Mon, 11 Mar 2013 09:32:12 +0100 [thread overview]
Message-ID: <513D968C.1060905@ladisch.de> (raw)
In-Reply-To: <1362973920-4942-1-git-send-email-helstroom@google.com>
David Helstroom wrote:
> Interface 1 does not exist
Then it doesn't need a quirk, does it?
> and Interface 0 should be ignored.
Why?
If the driver doesn't like something in interface 0, that bug should be
fixed.
What is the output of "lsusb -v" for this device?
Regards,
Clemens
next prev parent reply other threads:[~2013-03-11 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 3:52 [PATCH][RESEND] Add a USB audio quirk for the NuForce UDH-100 device David Helstroom
2013-03-11 8:32 ` Clemens Ladisch [this message]
2013-03-11 18:03 ` Dave Helstroom
2013-03-11 19:15 ` Clemens Ladisch
2013-03-11 23:58 ` Dave Helstroom
2013-03-12 7:36 ` Takashi Iwai
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=513D968C.1060905@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=damien@zamaudio.com \
--cc=eldad@fogrefinery.com \
--cc=helstroom@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pete.leigh@gmail.com \
--cc=tiwai@suse.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