From: Marcel Holtmann <marcel@holtmann.org>
To: Jesse Sung <jesse.sung@canonical.com>
Cc: linux-bluetooth@vger.kernel.org, 854399@bugs.launchpad.net
Subject: Re: [PATCH] Bluetooth: Add support for Broadcom BCM20702A0.
Date: Wed, 21 Sep 2011 09:53:28 +0200 [thread overview]
Message-ID: <1316591610.1937.107.camel@aeonflux> (raw)
In-Reply-To: <4E794037.6090809@canonical.com>
Hi Jesse,
> btusb would not take care of this device without its id in the table.
>
> If the output of usb-devices is still needed, please let me know.
yes, I just wanna see usb-devices and not go through 3 pages of verbose
lsusb output since that is not helping me.
Regards
Marcel
next prev parent reply other threads:[~2011-09-21 7:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 7:29 [PATCH] Bluetooth: Add support for Broadcom BCM20702A0 Jesse Sung
2011-09-20 13:05 ` Marcel Holtmann
2011-09-21 1:39 ` Jesse Sung
2011-09-21 7:53 ` Marcel Holtmann [this message]
2011-09-21 14:57 ` Jesse Sung
2011-10-25 8:41 ` Jesse Sung
2011-09-21 8:45 ` Oliver Neukum
2011-10-31 19:33 ` Gustavo Padovan
2011-11-08 6:51 ` Jesse Sung
2011-11-08 15:34 ` Gustavo Padovan
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=1316591610.1937.107.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=854399@bugs.launchpad.net \
--cc=jesse.sung@canonical.com \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).