devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 1/3] ARM: tegra: acer-a500: Correct compatible of ak8975 magnetometer
Date: Mon, 4 Oct 2021 22:40:27 +0200	[thread overview]
Message-ID: <YVtmuxnL0NVpWYGv@orome.fritz.box> (raw)
In-Reply-To: <20210926233704.10164-2-digetx@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

On Mon, Sep 27, 2021 at 02:37:02AM +0300, Dmitry Osipenko wrote:
> From: David Heidelberg <david@ixit.cz>
> 
> The "ak,ak8975" compatible is not recognized by dt-bindings, it's
> deprecated. Use supported "asahi-kasei,ak8975" compatible.
> 
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
>  arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-10-04 20:40 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 [this message]
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

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=YVtmuxnL0NVpWYGv@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).