From: Marcel Holtmann <marcel@holtmann.org>
To: David Lechner <david@lechnology.com>
Cc: devicetree <devicetree@vger.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560
Date: Wed, 13 Dec 2017 09:39:10 +0100 [thread overview]
Message-ID: <12AF86F1-0F4F-40E5-9139-8B175A8F3269@holtmann.org> (raw)
In-Reply-To: <1513124971-23717-1-git-send-email-david@lechnology.com>
Hi David,
> This series updates the bindings TI WiLink 7/8 Bluetooth to add TI CC256x
> chips as well. A compatible string is also added to the hci_ll driver for
> TI CC2560.
>
> David Lechner (2):
> dt-bindings: net: add TI CC2560 Bluetooth chip
> Bluetooth: hci_ll: add "ti,cc2560" compatible string
>
> .../bindings/net/{ti,wilink-st.txt => ti-bluetooth.txt} | 13 +++++++++++--
> drivers/bluetooth/hci_ll.c | 1 +
> 2 files changed, 12 insertions(+), 2 deletions(-)
> rename Documentation/devicetree/bindings/net/{ti,wilink-st.txt => ti-bluetooth.txt} (78%)
both patches have been applied to bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2017-12-13 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 0:29 [PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560 David Lechner
2017-12-13 0:29 ` [PATCH 1/2] dt-bindings: net: add TI CC2560 Bluetooth chip David Lechner
[not found] ` <1513124971-23717-2-git-send-email-david-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-12-15 23:05 ` Rob Herring
[not found] ` <1513124971-23717-1-git-send-email-david-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-12-13 0:29 ` [PATCH 2/2] Bluetooth: hci_ll: add "ti,cc2560" compatible string David Lechner
2017-12-13 8:39 ` Marcel Holtmann [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=12AF86F1-0F4F-40E5-9139-8B175A8F3269@holtmann.org \
--to=marcel@holtmann.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).