From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Heiko Stuebner <heiko@sntech.de>
Cc: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: fix LDO_REG4 / LDO_REG7 confusion on rk3368-lion
Date: Fri, 24 Sep 2021 00:24:57 +0200 [thread overview]
Message-ID: <163243587941.2556919.15754379297611690432.b4-ty@sntech.de> (raw)
In-Reply-To: <20210922230429.2162535-1-heiko@sntech.de>
On Thu, 23 Sep 2021 01:04:27 +0200, Heiko Stuebner wrote:
> LDO_REG7 is used for generating VCC_18.
> LDO_REG4 is not connected to anything - delete it.
Applied, thanks!
[1/3] arm64: dts: rockchip: fix LDO_REG4 / LDO_REG7 confusion on rk3368-lion
commit: 3bd7f3ef3b0f34aefcd09e2e834bbee868179b09
[2/3] arm64: dts: rockchip: define iodomains for rk3368-lion
commit: 0ed6b51dfde601c8b815a81aab701cd8965c5b12
[3/3] arm64: dts: rockchip: add phandles to muxed i2c buses on rk3368-lion
commit: 5a73d7ca7f7a64144e03ef0fc8eb6f8e5ea54df3
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2021-09-23 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 23:04 [PATCH 1/3] arm64: dts: rockchip: fix LDO_REG4 / LDO_REG7 confusion on rk3368-lion Heiko Stuebner
2021-09-22 23:04 ` [PATCH 2/3] arm64: dts: rockchip: define iodomains for rk3368-lion Heiko Stuebner
2021-09-22 23:04 ` [PATCH 3/3] arm64: dts: rockchip: add phandles to muxed i2c buses on rk3368-lion Heiko Stuebner
2021-09-23 22:24 ` Heiko Stuebner [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=163243587941.2556919.15754379297611690432.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=jakob.unterwurzacher@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).