From: Heiko Stuebner <heiko@sntech.de>
To: "Aditya Prayoga" <aditya@kobol.io>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Johan Jonker <jbx6244@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] arm64: Add basic support for Kobol's Helios64
Date: Mon, 2 Nov 2020 15:55:45 +0100 [thread overview]
Message-ID: <160432890189.1244997.12717967728600775929.b4-ty@sntech.de> (raw)
In-Reply-To: <20201014200030.845759-1-uwe@kleine-koenig.org>
On Wed, 14 Oct 2020 22:00:28 +0200, Uwe Kleine-König wrote:
> in v3 Johan still found some inconsistencies in how I sorted (or didn't
> sort) the device tree properties. The rules I applied now are:
>
> at the beginning of a node: compatible, reg and interrupt stuff
> status and #* at the end
> i2c-scl-rising-time-ns before i2c-scl-falling-time-ns
> regulator-name first among regulator-*
> regulator-min-microvolt before regulator-max-microvolt
> pinctrl-names before pinctrl-0
> tx_delay grouped with (and after) rx_delay
> vcc12* after vcc5*
> otherwise alphabetically
>
> [...]
Applied, thanks!
[1/2] dt-bindings: vendor-prefixes: Add kobol prefix
commit: fa67f2817ff2c9bb07472d30e58d904922f1a538
[2/2] arm64: dts: rockchip: Add basic support for Kobol's Helios64
commit: 09e006cfb43e8ec38afe28278b210dab72e6cac8
Fixed spaces with tabs in the deleted opp area and
inserted a blank between the two cluster blocks.
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2020-11-02 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 20:00 [PATCH v4 0/2] arm64: Add basic support for Kobol's Helios64 Uwe Kleine-König
2020-10-14 20:00 ` [PATCH v4 1/2] dt-bindings: vendor-prefixes: Add kobol prefix Uwe Kleine-König
2020-10-16 16:20 ` Rob Herring
2020-10-17 21:31 ` Uwe Kleine-König
2020-10-14 20:00 ` [PATCH v4 2/2] arm64: dts: rockchip: Add basic support for Kobol's Helios64 Uwe Kleine-König
2020-11-02 14:55 ` 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=160432890189.1244997.12717967728600775929.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=aditya@kobol.io \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=uwe@kleine-koenig.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).