From: Gustavo Padovan <padovan@profusion.mobi>
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: Mon, 31 Oct 2011 17:33:54 -0200 [thread overview]
Message-ID: <20111031193354.GG10164@joana> (raw)
In-Reply-To: <4E7840CF.5010805@canonical.com>
Hi Jesse,
* Jesse Sung <jesse.sung@canonical.com> [2011-09-20 15:29:19 +0800]:
> Add a new entry (413c:8197) to device ID table.
Can I get the output of usbdevices in the commit message, please. Then we can
prove that adding it to the device ID table is really necessary.
Gustavo
next prev parent reply other threads:[~2011-10-31 19:33 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
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 [this message]
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=20111031193354.GG10164@joana \
--to=padovan@profusion.mobi \
--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).