From: Marcel Holtmann <marcel@holtmann.org>
To: John-Eric Kamps <johnny86@gmx.de>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: hci_h5: Add support for binding RTL8723DS with device tree
Date: Wed, 6 Jan 2021 08:50:09 +0100 [thread overview]
Message-ID: <B3488D5C-B436-42E6-B488-96E5E8E84463@holtmann.org> (raw)
In-Reply-To: <20210102214116.1098030-1-johnny86@gmx.de>
Hi John-Eric,
> RTL8723DS could be handled by btrtl-driver, so add ability to bind it
> using device tree.
>
> Signed-off-by: John-Eric Kamps <johnny86@gmx.de>
> ---
> drivers/bluetooth/hci_h5.c | 2 ++
> 1 file changed, 2 insertions(+)
patch has been applied to bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2021-01-06 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 21:41 [PATCH 2/2] Bluetooth: hci_h5: Add support for binding RTL8723DS with device tree John-Eric Kamps
2021-01-06 7:50 ` 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=B3488D5C-B436-42E6-B488-96E5E8E84463@holtmann.org \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--cc=johnny86@gmx.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).