From: Arend van Spriel <arend@broadcom.com>
To: Ilya Faenson <ifaenson@broadcom.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 0/5] Broadcom Bluetooth UART device driver
Date: Thu, 4 Jun 2015 09:44:36 +0200 [thread overview]
Message-ID: <557001E4.6030000@broadcom.com> (raw)
In-Reply-To: <1433365304-16707-1-git-send-email-ifaenson@broadcom.com>
On 06/03/15 23:01, Ilya Faenson wrote:
> This is a merge of the Broadcom Bluetooth UART logic with
> the latest line discipline and protocol enhancements implemented
> by Frederic Danis of Intel.
The series from Frederic Danis can be found by its message-id:
1432805106-25719-1-git-send-email-frederic.danis@linux.intel.com
Regards,
Arend
[1]
http://mid.gmane.org/1432805106-25719-1-git-send-email-frederic.danis@linux.intel.com
> Ilya Faenson (5):
> Broadcom Bluetooth UART Device Tree bindings
> Intel based H4 line discipline enhancements
> Broadcom Bluetooth UART Platform Driver
> Broadcom Bluetooth protocol UART support
> BlueZ Broadcom UART Protocol
>
> .../devicetree/bindings/net/bluetooth/btbcm.txt | 82 +++
> drivers/bluetooth/Kconfig | 9 +
> drivers/bluetooth/Makefile | 1 +
> drivers/bluetooth/btbcm.c | 142 ++++-
> drivers/bluetooth/btbcm.h | 21 +-
> drivers/bluetooth/btbcm_uart.c | 673 +++++++++++++++++++++
> drivers/bluetooth/btbcm_uart.h | 89 +++
> drivers/bluetooth/hci_bcm.c | 481 ++++++++++++++-
> drivers/bluetooth/hci_ldisc.c | 110 +++-
> drivers/bluetooth/hci_uart.h | 6 +
> 10 files changed, 1565 insertions(+), 49 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/bluetooth/btbcm.txt
> create mode 100755 drivers/bluetooth/btbcm_uart.c
> create mode 100755 drivers/bluetooth/btbcm_uart.h
>
next prev parent reply other threads:[~2015-06-04 7:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 21:01 [PATCH 0/5] Broadcom Bluetooth UART device driver Ilya Faenson
2015-06-03 21:01 ` [PATCH 1/5] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
2015-06-06 6:40 ` Marcel Holtmann
2015-06-06 7:41 ` Arend van Spriel
2015-06-06 8:33 ` Marcel Holtmann
2015-06-06 11:26 ` Arend van Spriel
2015-06-07 7:39 ` Marcel Holtmann
2015-06-03 21:01 ` [PATCH 2/5] Intel based H4 line discipline enhancements Ilya Faenson
2015-06-06 6:36 ` Marcel Holtmann
2015-06-06 15:33 ` Ilya Faenson
2015-06-06 15:40 ` Arend van Spriel
2015-06-06 16:39 ` Marcel Holtmann
2015-06-06 17:48 ` Peter Hurley
2015-06-06 18:24 ` Ilya Faenson
2015-06-06 15:50 ` Marcel Holtmann
2015-06-06 18:25 ` Ilya Faenson
2015-06-03 21:01 ` [PATCH 3/5] Broadcom Bluetooth UART Platform Driver Ilya Faenson
2015-06-04 8:41 ` Frederic Danis
2015-06-03 21:01 ` [PATCH 4/5] Broadcom Bluetooth protocol UART support Ilya Faenson
2015-06-06 6:37 ` Marcel Holtmann
2015-06-06 8:15 ` Arend van Spriel
2015-06-06 8:31 ` Marcel Holtmann
2015-06-06 16:03 ` chanyeol
2015-06-03 21:01 ` [PATCH 5/5] BlueZ Broadcom UART Protocol Ilya Faenson
2015-06-04 10:14 ` Frederic Danis
2015-06-04 11:13 ` Arend van Spriel
2015-06-04 7:44 ` Arend van Spriel [this message]
2015-06-04 16:00 ` [PATCH 0/5] Broadcom Bluetooth UART device driver Frederic Danis
2015-06-04 23:46 ` Ilya Faenson
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=557001E4.6030000@broadcom.com \
--to=arend@broadcom.com \
--cc=ifaenson@broadcom.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).