From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>,
Satya Priya <skakit@codeaurora.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Heidelberg <david@ixit.cz>, Andy Gross <agross@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
Caleb Connolly <caleb@connolly.tech>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rtc: qcom-pm8xxx-rtc: update register numbers
Date: Wed, 5 Jan 2022 01:09:48 +0100 [thread overview]
Message-ID: <164134138455.1689308.13953697422685161107.b4-ty@bootlin.com> (raw)
In-Reply-To: <20211213192946.111320-1-david@ixit.cz>
On Mon, 13 Dec 2021 20:29:45 +0100, David Heidelberg wrote:
> Extend registers up to 2, also document their names.
>
> Also fixes warnings generated by `make qcom/sdm845-oneplus-fajita.dtb`:
> arch/arm64/boot/dts/qcom/sdm845-oneplus-fajita.dt.yaml: rtc@6000: reg: [[24576], [24832]] is too long
> From schema: Documentation/devicetree/bindings/rtc/qcom-pm8xxx-rtc.yaml
> arch/arm64/boot/dts/qcom/sdm845-oneplus-fajita.dt.yaml: rtc@6000: 'reg-names' does not match any of the regexes: 'pinctrl-[0-9]+'
> From schema: Documentation/devicetree/bindings/rtc/qcom-pm8xxx-rtc.yaml
>
> [...]
Applied, thanks!
[1/1] dt-bindings: rtc: qcom-pm8xxx-rtc: update register numbers
commit: a12ac1f0ffa41b7aab3f69c4aac5bb72369bd117
Best regards,
--
Alexandre Belloni <alexandre.belloni@bootlin.com>
prev parent reply other threads:[~2022-01-05 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 19:29 David Heidelberg
2021-12-13 23:23 ` Rob Herring
2021-12-14 16:22 ` David Heidelberg
2021-12-15 20:23 ` Rob Herring
2021-12-15 20:24 ` Rob Herring
2022-01-05 0:09 ` Alexandre Belloni [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=164134138455.1689308.13953697422685161107.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=caleb@connolly.tech \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=skakit@codeaurora.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
all inboxes | Powered by JetHome®