From: Heiko Stuebner <heiko@sntech.de>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Levin Du <djw@t-chip.com.cn>, Akash Gajjar <akash@openedev.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Da Xue <da@lessconfused.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-amarula@amarulasolutions.com
Subject: Re: [PATCH 5/6] arm64: dts: rockchip: Rename vcc12v_sys into dc_12v for roc-rk3399-pc
Date: Fri, 04 Oct 2019 00:49:42 +0200 [thread overview]
Message-ID: <2645663.MEMbyMBloX@phil> (raw)
In-Reply-To: <20190919052822.10403-6-jagan@amarulasolutions.com>
Am Donnerstag, 19. September 2019, 07:28:21 CEST schrieb Jagan Teki:
> It is always better practice to follow regulator naming conventions
> as per the schematics for future references.
>
> This would indeed helpful to review and check the naming convention
> directly on schematics, both for the code reviewers and the developers.
>
> So, rename vcc12v_sys into dc_12v as per rk3399 power tree as per
> roc-rk3399-pc schematics.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
applied for 5.5 (with the filename changed to the current one of course)
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Da Xue <da@lessconfused.com>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Akash Gajjar <akash@openedev.com>, Levin Du <djw@t-chip.com.cn>,
linux-amarula@amarulasolutions.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/6] arm64: dts: rockchip: Rename vcc12v_sys into dc_12v for roc-rk3399-pc
Date: Fri, 04 Oct 2019 00:49:42 +0200 [thread overview]
Message-ID: <2645663.MEMbyMBloX@phil> (raw)
In-Reply-To: <20190919052822.10403-6-jagan@amarulasolutions.com>
Am Donnerstag, 19. September 2019, 07:28:21 CEST schrieb Jagan Teki:
> It is always better practice to follow regulator naming conventions
> as per the schematics for future references.
>
> This would indeed helpful to review and check the naming convention
> directly on schematics, both for the code reviewers and the developers.
>
> So, rename vcc12v_sys into dc_12v as per rk3399 power tree as per
> roc-rk3399-pc schematics.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
applied for 5.5 (with the filename changed to the current one of course)
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-03 22:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 5:28 [PATCH 0/6] arm64: dts: rockchip: ROC-PC fixes Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-09-19 5:28 ` [PATCH 1/6] arm64: dts: rockchip: Fix rk3399-roc-pc pwm2 pin Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-09-29 21:21 ` Heiko Stuebner
2019-09-29 21:21 ` Heiko Stuebner
2019-09-29 21:21 ` Heiko Stuebner
2019-10-01 10:26 ` Jagan Teki
2019-10-01 10:26 ` Jagan Teki
2019-10-01 10:34 ` Michael Nazzareno Trimarchi
2019-10-01 10:34 ` Michael Nazzareno Trimarchi
2019-10-08 3:11 ` djw
2019-10-08 3:11 ` djw
2019-10-08 3:11 ` djw
2019-10-16 17:09 ` Jagan Teki
2019-10-16 17:09 ` Jagan Teki
2019-10-17 13:26 ` Markus Reichl
2019-10-17 13:26 ` Markus Reichl
2019-10-17 13:49 ` Jagan Teki
2019-10-17 13:49 ` Jagan Teki
2019-10-17 23:33 ` Heiko Stuebner
2019-10-17 23:33 ` Heiko Stuebner
2019-10-22 6:19 ` djw
2019-10-22 6:19 ` djw
2019-10-22 6:19 ` djw
2019-09-19 5:28 ` [PATCH 2/6] dt-bindings: arm: rockchip: Use libretech for roc-pc binding Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-09-19 5:28 ` [PATCH 3/6] arm64: dts: rockchip: Use libretech model, compatible for ROC-PC Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-09-19 5:28 ` [PATCH 4/6] arm64: dts: rockchip: Rename roc-pc with libretech notation Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-09-29 21:32 ` Heiko Stuebner
2019-09-29 21:32 ` Heiko Stuebner
2019-09-29 21:32 ` Heiko Stuebner
2019-10-01 10:33 ` Jagan Teki
2019-10-01 10:33 ` Jagan Teki
2019-10-01 11:01 ` Chen-Yu Tsai
2019-10-01 11:01 ` Chen-Yu Tsai
2019-10-01 11:01 ` Chen-Yu Tsai
2019-09-19 5:28 ` [PATCH 5/6] arm64: dts: rockchip: Rename vcc12v_sys into dc_12v for roc-rk3399-pc Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-10-03 22:49 ` Heiko Stuebner [this message]
2019-10-03 22:49 ` Heiko Stuebner
2019-09-19 5:28 ` [PATCH 6/6] arm64: dts: rockchip: Fix roc-rk3399-pc regulator input rails Jagan Teki
2019-09-19 5:28 ` Jagan Teki
2019-10-03 22:50 ` Heiko Stuebner
2019-10-03 22:50 ` Heiko Stuebner
[not found] ` <20190919052822.10403-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-10-16 17:11 ` [PATCH 0/6] arm64: dts: rockchip: ROC-PC fixes Jagan Teki
2019-10-16 17:11 ` Jagan Teki
2019-10-16 17:11 ` Jagan Teki
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=2645663.MEMbyMBloX@phil \
--to=heiko@sntech.de \
--cc=akash@openedev.com \
--cc=da@lessconfused.com \
--cc=devicetree@vger.kernel.org \
--cc=djw@t-chip.com.cn \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.