From: Rob Herring <robh@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: heiko@sntech.de, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, lee.jones@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v1 1/5] dt-binding: mfd: syscon: add Rockchip QoS register compatibles
Date: Mon, 9 Nov 2020 16:03:12 -0600 [thread overview]
Message-ID: <20201109220312.GA1835439@bogus> (raw)
In-Reply-To: <20201107170103.25608-1-jbx6244@gmail.com>
On Sat, 07 Nov 2020 18:00:59 +0100, Johan Jonker wrote:
> With the conversion of syscon.yaml minItems for compatibles
> was set to 2. Current Rockchip dtsi files only use "syscon" for
> QoS registers. Add Rockchip QoS compatibles to reduce notifications
> produced with:
>
> make ARCH=arm dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/mfd/syscon.yaml
>
> make ARCH=arm64 dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/mfd/syscon.yaml
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-11-09 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 17:00 [PATCH v1 1/5] dt-binding: mfd: syscon: add Rockchip QoS register compatibles Johan Jonker
2020-11-07 17:01 ` [PATCH v1 2/5] ARM: dts: rockchip: add QoS register compatibles for rk3066/rk3188 Johan Jonker
2020-11-07 17:01 ` [PATCH v1 3/5] ARM: dts: rockchip: add QoS register compatibles for rk3288 Johan Jonker
2020-11-07 17:01 ` [PATCH v1 4/5] arm64: dts: rockchip: add QoS register compatibles for rk3399 Johan Jonker
2020-11-07 17:01 ` [PATCH v1 5/5] arm64: dts: rockchip: add QoS register compatibles for px30 Johan Jonker
2020-11-09 22:03 ` Rob Herring [this message]
2020-11-13 10:01 ` [PATCH v1 1/5] dt-binding: mfd: syscon: add Rockchip QoS register compatibles Lee Jones
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=20201109220312.GA1835439@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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).