linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [RFC v3 0/4] Broadcom Bluetooth UART device driver
Date: Tue, 19 May 2015 10:19:56 +0200	[thread overview]
Message-ID: <555AF22C.7000108@broadcom.com> (raw)
In-Reply-To: <1431553823-25670-1-git-send-email-ifaenson@broadcom.com>

On 05/13/15 23:50, Ilya Faenson wrote:
> The next version of the driver changed as per Marcel's comments.

This is just a cover letter and as such not stored in the git 
repository, but it is stored in the mailing list archives so I would 
recommend giving a short description here about what this patch series 
provides followed by a change log so you can keep the description and 
indicate in the change log what was done in the next version.

Regards,
Arend

> Ilya Faenson (4):
>    Broadcom Bluetooth UART Device Tree bindings
>    Broadcom Bluetooth UART Platform Driver
>    Broadcom Bluetooth protocol UART support
>    BlueZ Broadcom UART Protocol
>
>   .../devicetree/bindings/net/bluetooth/btbcm.txt    |  54 ++
>   drivers/bluetooth/Kconfig                          |   9 +
>   drivers/bluetooth/Makefile                         |   1 +
>   drivers/bluetooth/btbcm.c                          | 155 ++++-
>   drivers/bluetooth/btbcm.h                          |  13 +
>   drivers/bluetooth/btbcm_uart.c                     | 705 +++++++++++++++++++++
>   drivers/bluetooth/btbcm_uart.h                     | 116 ++++
>   drivers/bluetooth/hci_bcm.c                        | 528 ++++++++++++++-
>   8 files changed, 1561 insertions(+), 20 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/net/bluetooth/btbcm.txt
>   create mode 100644 drivers/bluetooth/btbcm_uart.c
>   create mode 100644 drivers/bluetooth/btbcm_uart.h
>

      parent reply	other threads:[~2015-05-19  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 21:50 [RFC v3 0/4] Broadcom Bluetooth UART device driver Ilya Faenson
2015-05-13 21:50 ` [RFC v3 1/4] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
2015-05-19  9:22   ` Arend van Spriel
2015-05-22 19:05     ` Ilya Faenson
2015-05-13 21:50 ` [RFC v3 2/4] Broadcom Bluetooth UART Platform Driver Ilya Faenson
2015-05-19 12:42   ` Arend van Spriel
2015-05-22 19:05     ` Ilya Faenson
2015-05-13 21:50 ` [RFC v3 3/4] Broadcom Bluetooth protocol UART support Ilya Faenson
2015-05-13 21:50 ` [RFC v3 4/4] BlueZ Broadcom UART Protocol Ilya Faenson
2015-05-19 12:47   ` Arend van Spriel
2015-05-19 15:20     ` Marcel Holtmann
2015-05-20  7:19       ` Arend van Spriel
2015-05-19  8:19 ` Arend van Spriel [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=555AF22C.7000108@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).