From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
David Heidelberg <david@ixit.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 3/3] ARM: tegra: Update Broadcom Bluetooth device-tree nodes
Date: Mon, 4 Oct 2021 22:41:02 +0200 [thread overview]
Message-ID: <YVtm3sivqqpeaz3T@orome.fritz.box> (raw)
In-Reply-To: <20210926233704.10164-4-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Mon, Sep 27, 2021 at 02:37:04AM +0300, Dmitry Osipenko wrote:
> The host-wakeup GPIO is now marked as deprecated in the broadcom-bluetooth
> device-tree binding, it's replaced with the host-wakeup interrupt. Update
> Tegra device-trees to the recent version of the Bluetooth binding.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 5 ++++-
> arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi | 5 ++++-
> arch/arm/boot/dts/tegra30-ouya.dts | 5 ++++-
> 3 files changed, 12 insertions(+), 3 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-10-04 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 23:37 [PATCH v1 0/3] Tegra ARM32 device-tree improvements for 5.16 Dmitry Osipenko
2021-09-26 23:37 ` [PATCH v1 1/3] ARM: tegra: acer-a500: Correct compatible of ak8975 magnetometer Dmitry Osipenko
2021-10-04 20:40 ` Thierry Reding
2021-09-26 23:37 ` [PATCH v1 2/3] ARM: tegra: Name clock and regulator nodes according to DT-schema Dmitry Osipenko
2021-10-04 20:56 ` Thierry Reding
2021-10-24 19:08 ` Dmitry Osipenko
2021-09-26 23:37 ` [PATCH v1 3/3] ARM: tegra: Update Broadcom Bluetooth device-tree nodes Dmitry Osipenko
2021-10-04 20:41 ` Thierry Reding [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=YVtm3sivqqpeaz3T@orome.fritz.box \
--to=thierry.reding@gmail.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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).