From: Rob Herring <robh@kernel.org>
To: David Summers <beagleboard@davidjohnsummers.uk>
Cc: mark.rutland@arm.com, marcel@holtmann.org,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Bluetooth: dt-bindings: Realtek serial bluetooth
Date: Mon, 21 Jan 2019 09:28:04 -0600 [thread overview]
Message-ID: <20190121152804.GA29172@bogus> (raw)
In-Reply-To: <20190120124046.6715-1-beagleboard@davidjohnsummers.uk>
On Sun, Jan 20, 2019 at 12:40:45PM +0000, David Summers wrote:
> Since v2, the compatible binding names have been changed to end in
> -bt, as requested by robh.
Now you have the same subject for 2 different patches. Again, use
'git log --oneline drivers/bluetooth/hci_h5.c' and follow the subject
pattern.
> Signed-off-by: David Summers <beagleboard@davidjohnsummers.uk>
> ---
> drivers/bluetooth/hci_h5.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
> index 8eede1197cd2..056ab2decccc 100644
> --- a/drivers/bluetooth/hci_h5.c
> +++ b/drivers/bluetooth/hci_h5.c
> @@ -925,6 +925,22 @@ static struct h5_vnd rtl_vnd = {
> };
> #endif
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id h5_of_match[] = {
> +#ifdef CONFIG_BT_HCIUART_RTL
> + { .compatible = "realtek,rtl8723as-bt"},
> + { .compatible = "realtek,rtl8723bs-bt"},
> + { .compatible = "realtek,rtl8723ds-bt"},
> + { .compatible = "realtek,rtl8761atv"},
> + { .compatible = "realtek,rtl8821as-bt"},
> + { .compatible = "realtek,rtl8821cs-bt"},
> + { .compatible = "realtek,rtl8822bs-bt"},
> +#endif
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, h5_of_match);
> +#endif
> +
> #ifdef CONFIG_ACPI
> static const struct acpi_device_id h5_acpi_match[] = {
> #ifdef CONFIG_BT_HCIUART_RTL
> --
> beagleboard@davidjohnsummers.uk
>
prev parent reply other threads:[~2019-01-21 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 12:40 [PATCH v3 1/2] Bluetooth: dt-bindings: Realtek serial bluetooth David Summers
2019-01-20 12:40 ` [PATCH v3 2/2] " David Summers
2019-01-21 14:46 ` Marcel Holtmann
2019-01-21 15:28 ` Rob Herring [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=20190121152804.GA29172@bogus \
--to=robh@kernel.org \
--cc=beagleboard@davidjohnsummers.uk \
--cc=devicetree@vger.kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.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).