From: Andrew Morton <akpm@linux-foundation.org>
To: David Griffith <dgriffi@cs.csubak.edu>
Cc: Vitaliy Ivanov <vitalivanov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>,
linux-usb-devel@lists.sourceforge.net,
Jaroslav Kysela <perex@suse.cz>, Takashi Iwai <tiwai@suse.de>
Subject: Re: fixing usb-midi device support
Date: Mon, 5 Nov 2007 19:21:53 -0800 [thread overview]
Message-ID: <20071105192153.2bbae10f.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.GSO.4.55.0711011018360.13024@helios.cs.csubak.edu>
On Thu, 1 Nov 2007 10:20:24 -0700 (PDT) David Griffith <dgriffi@cs.csubak.edu> wrote:
> On Thu, 1 Nov 2007, Vitaliy Ivanov wrote:
Lots of cc's added.
> > David,
> >
> > On 10/31/07, David Griffith <dgriffi@cs.csubak.edu> wrote:
> > >
> > > I have a MOTU Fastlane and an Emu Xmidi 2x2 USB midi interfaces. The Emu
> > > unit works fine with current kernels. The MOTU unit won't work with
> > > kernels newer than 2.6.17.
It's a regression.
> I stumbled over a patch that had something to
> > > do with a MOTU Fastlane, but I haven't been able to find it again. Could
> > > I get some advice on fixing MOTU Fastlane support?
> >
> > I can see that you already had a discussion on this issue:
> > http://lkml.org/lkml/2007/8/10/102
> >
> > Any results? Do you still can see the oops?
>
> The oops is still present. I was hoping that the patch I found and lost
> would help me understand what was going on.
>
Are you able to send a copy of the oops output?
next prev parent reply other threads:[~2007-11-06 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:30 fixing usb-midi device support David Griffith
2007-11-01 10:46 ` Vitaliy Ivanov
2007-11-01 17:20 ` David Griffith
2007-11-06 3:21 ` Andrew Morton [this message]
2007-11-06 5:03 ` David Griffith
2007-11-06 9:17 ` [linux-usb-devel] " Oliver Neukum
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=20071105192153.2bbae10f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clemens@ladisch.de \
--cc=dgriffi@cs.csubak.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
--cc=vitalivanov@gmail.com \
/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.