From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chris Morgan <macromorgan@hotmail.com>
Cc: Chris Morgan <macroalpha82@gmail.com>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
heiko@sntech.de, pgwipeout@gmail.com, cphealy@gmail.com
Subject: Re: [PATCH v2 3/3] arm64: dts: rockchip: add Anbernic RG353P and RG503
Date: Tue, 23 Aug 2022 15:41:36 +0300 [thread overview]
Message-ID: <13858817-dbca-68b2-9905-cb7d0bc81cbd@linaro.org> (raw)
In-Reply-To: <SN6PR06MB534215A808939107AFDE5CFEA5709@SN6PR06MB5342.namprd06.prod.outlook.com>
On 23/08/2022 15:40, Chris Morgan wrote:
>>> + regulators {
>>> + vdd_logic: DCDC_REG1 {
>>
>> I commented here and there was no feedback, so please implement the change.
>>
>
> Sorry I didn't explicitly call it out, I only made a note in the
> revision notes. The regulator names for the RK808 series are hard-coded, so
> I can't change them without modifying the driver (and every existing DTS that
> uses them).
OK.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-08-23 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 22:25 [PATCH v2 0/3] Add Anbernic RG353P and RG503 Chris Morgan
2022-08-19 22:25 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add Anbernic Chris Morgan
2022-08-19 22:25 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add Anbernic RG353P and RG503 Chris Morgan
2022-08-19 22:25 ` [PATCH v2 3/3] arm64: dts: rockchip: add " Chris Morgan
2022-08-20 8:40 ` Maya Matuszczyk
2022-08-23 12:16 ` Heiko Stübner
2022-08-23 12:28 ` Maya Matuszczyk
2022-08-23 13:29 ` Chris Morgan
2022-08-23 12:28 ` Krzysztof Kozlowski
2022-08-23 12:36 ` Chris Morgan
2022-08-23 12:35 ` Chris Morgan
[not found] ` <20220823123529.GA9857@wintermute.localdomain>
2022-08-23 12:50 ` Chris Morgan
2022-08-23 12:28 ` Krzysztof Kozlowski
2022-08-23 12:26 ` Krzysztof Kozlowski
2022-08-23 12:40 ` Chris Morgan
2022-08-23 12:41 ` Krzysztof Kozlowski [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=13858817-dbca-68b2-9905-cb7d0bc81cbd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.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).