public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: David Fries <david@fries.net>
Cc: David Griffith <dgriffi@cs.csubak.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: bad endpoint address, MOTU FastLane
Date: Tue, 26 May 2009 09:25:57 +0200	[thread overview]
Message-ID: <4A1B9985.5060703@ladisch.de> (raw)
In-Reply-To: <20090526004146.GD4300@spacedout.fries.net>

David Fries wrote:
> On Mon, May 25, 2009 at 10:20:43AM +0200, Clemens Ladisch wrote:
> > David Fries wrote:
> > > The MOTU Fastlane device is the only one using QUIRK_MIDI_RAW.  How about
> > > changing the name to QUIRK_MIDI_FASTLANE to imply it isn't completely
> > > generic anymore and adding a comment?
> > 
> > And while we're at it, the driver should claim interface 1 to prevent
> > anyone else from using it.
> 
> Before and after the latest patch snd-usb-audio claims interface 1.

Oops.  Well, that makes the patch easier.  ;-)

> > New patch below.
> > 
> > Are you okay with the tested-by tag?
> 
> Yes, it works.  I'm watching the LEDs blink on the device and data
> come across.

Okay, I'll applay it in the sound tree.


Best regards,
Clemens

      reply	other threads:[~2009-05-26  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 22:12 bad endpoint address, MOTU FastLane David Fries
2009-05-12  7:55 ` Clemens Ladisch
2009-05-12 14:08   ` Alan Stern
2009-05-12 15:22     ` Todd T. Fries
2009-05-12 15:44       ` Alan Stern
2009-05-24 22:07   ` David Fries
2009-05-25  8:20     ` Clemens Ladisch
2009-05-26  0:41       ` David Fries
2009-05-26  7:25         ` Clemens Ladisch [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=4A1B9985.5060703@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=david@fries.net \
    --cc=dgriffi@cs.csubak.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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