From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V8 0/3] USB: OHCI: Start splitting up the driver
Date: Wed, 29 May 2013 20:08:10 +0200 [thread overview]
Message-ID: <3818608.3TBO8NnpYQ@wuerfel> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1305291211160.885-100000@iolanthe.rowland.org>
On Wednesday 29 May 2013 12:21:02 Alan Stern wrote:
>
> Those error messages are annoying; they don't use dev_err(), so they
> don't include the device and driver names. There's no way to know what
> they refer to. I rather suspect they come from the usbaudio driver.
That makes sense. I have a usb audio device, and I don't actually recall
getting any sound from my speakers while testing it. I only checked
that the mouse was working and assumed that the usb-audio was driven
by ehci, but upon closer inspection, they are both on the same OHCI.
> When you ran this test, did you have commit 815fa7b91761 applied?
Yes.
> Does the same problem occur without Manjunath's changes?
No, it was introduced by the first patch, as I found later.
Arnd
next prev parent reply other threads:[~2013-05-29 18:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1365746856-7772-2-git-send-email-manjunath.goudar@linaro.org>
2013-05-07 9:50 ` [RFC PATCH 0/2] USB: OHCI: Start splitting up the driver Manjunath Goudar
2013-05-07 9:50 ` [RFC PATCH 1/2] USB: OHCI: prepare to make ohci-hcd a library module Manjunath Goudar
2013-05-07 15:15 ` Alan Stern
2013-05-07 9:50 ` [RFC PATCH 2/2] USB: OHCI: make ohci-pci a separate driver Manjunath Goudar
2013-05-23 11:11 ` [RFC V6 PATCH 0/3] USB: OHCI: Start splitting up the driver Manjunath Goudar
2013-05-23 11:11 ` [RFC V6 PATCH 1/3] USB: OHCI: prepare to make ohci-hcd a library module Manjunath Goudar
2013-05-23 14:27 ` Alan Stern
2013-05-23 11:11 ` [RFC PATCH 2/3] USB: OHCI: Generic changes to make ohci-pci a separate driver Manjunath Goudar
2013-05-23 13:26 ` Arnd Bergmann
2013-05-23 14:30 ` Alan Stern
2013-05-23 11:11 ` [RFC V6 PATCH 3/3] USB: OHCI: " Manjunath Goudar
2013-05-23 14:37 ` Alan Stern
2013-05-23 17:01 ` Arnd Bergmann
2013-05-23 17:37 ` Alan Stern
2013-05-23 17:42 ` Arnd Bergmann
2013-05-27 12:25 ` [RFC V7 PATCH 0/3] USB: OHCI: Start splitting up the driver Manjunath Goudar
2013-05-27 12:25 ` [RFC V7 PATCH 1/3] USB: OHCI: prepare to make ohci-hcd a library module Manjunath Goudar
2013-05-27 14:54 ` Alan Stern
2013-05-27 12:25 ` [RFC V7 PATCH 2/3] USB: OHCI: Generic changes to make ohci-pci a separate driver Manjunath Goudar
2013-05-27 14:55 ` Alan Stern
2013-05-27 12:25 ` [RFC V7 PATCH 3/3] USB: OHCI: " Manjunath Goudar
2013-05-27 14:58 ` Alan Stern
2013-05-27 20:38 ` Arnd Bergmann
2013-05-27 13:29 ` [RFC V7 PATCH 0/3] USB: OHCI: Start splitting up the driver Viresh Kumar
2013-05-28 13:04 ` [PATCH V8 " Manjunath Goudar
2013-05-28 13:04 ` [PATCH V8 1/3] USB: OHCI: prepare to make ohci-hcd a library module Manjunath Goudar
2013-05-28 13:04 ` [PATCH V8 2/3] USB: OHCI: Generic changes to make ohci-pci a separate driver Manjunath Goudar
2013-05-28 13:04 ` [PATCH V8 3/3] USB: OHCI: " Manjunath Goudar
2013-05-28 15:27 ` Alan Stern
2013-05-28 20:11 ` [PATCH V8 0/3] USB: OHCI: Start splitting up the driver Arnd Bergmann
2013-05-29 16:21 ` Alan Stern
2013-05-29 18:08 ` Arnd Bergmann [this message]
2013-05-29 18:16 ` Alan Stern
2013-05-29 22:02 ` Arnd Bergmann
2013-05-31 14:12 ` Alan Stern
2013-05-31 14:57 ` Arnd Bergmann
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=3818608.3TBO8NnpYQ@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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