From: Gustavo Padovan <padovan@profusion.mobi>
To: Oliver Neukum <oneukum@suse.de>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] btusb: add device entry for Broadcom SoftSailing
Date: Thu, 29 Sep 2011 16:34:34 -0300 [thread overview]
Message-ID: <20110929193434.GE2605@joana> (raw)
In-Reply-To: <201109211141.45978.oneukum@suse.de>
Hi Oliver,
* Oliver Neukum <oneukum@suse.de> [2011-09-21 11:41:45 +0200]:
> From 0cea73465cd22373c5cd43a3edd25fbd4bb532ef Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oliver@neukum.org>
> Date: Wed, 21 Sep 2011 11:37:15 +0200
> Subject: [PATCH] btusb: add device entry for Broadcom SoftSailing
>
> This device declares itself to be vendor specific
> It therefore needs to be added to the device table
> to make btusb bind.
>
> Signed-off-by: Oliver Neukum <oneukum@suse.de>
Applied, thanks.
Gustavo
prev parent reply other threads:[~2011-09-29 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 9:41 [PATCH] btusb: add device entry for Broadcom SoftSailing Oliver Neukum
2011-09-29 19:34 ` Gustavo Padovan [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=20110929193434.GE2605@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=oneukum@suse.de \
/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).