From: Maxime Ripard <maxime@cerno.tech>
To: Samuel Holland <samuel@sholland.org>
Cc: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH] arm64: dts: allwinner: a64: pinetab: Fix cpvdd supply name
Date: Mon, 4 May 2020 12:53:52 +0200 [thread overview]
Message-ID: <20200504105352.m7x3yo7ne2j2goas@gilmour.lan> (raw)
In-Reply-To: <20200426162353.52465-1-samuel@sholland.org>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Sun, Apr 26, 2020 at 11:23:53AM -0500, Samuel Holland wrote:
> An older version of the analog codec binding referenced the headphone
> amplifier binding as "hpvcc". However, by the time it was merged in
> commit 21dd30200e3d ("ASoC: dt-bindings: sun50i-codec-analog: Add
> headphone amp regulator supply"), the regulator reference was renamed to
> "cpvdd". This board's device tree still uses the old name, which fails
> to work at runtime, and which causes a warning from `make dtbs_check`.
> Resolve both by fixing the name.
>
> Fixes: 674ef1d0a7b2 ("arm64: dts: allwinner: a64: add support for PineTab")
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Applied, thanks!
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-05-04 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 16:23 [PATCH] arm64: dts: allwinner: a64: pinetab: Fix cpvdd supply name Samuel Holland
2020-05-04 10:53 ` Maxime Ripard [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=20200504105352.m7x3yo7ne2j2goas@gilmour.lan \
--to=maxime@cerno.tech \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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).