From: Rob Herring <robh+dt@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: satya priya <skakit@codeaurora.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, Kiran Gunda <kgunda@codeaurora.org>
Subject: Re: [PATCH V2 3/4] dt-bindings: mfd: Convert pm8xxx bindings to yaml
Date: Fri, 16 Apr 2021 12:20:30 -0500 [thread overview]
Message-ID: <CAL_JsqKYQ2EBgQJzKJSy-+D20Pmu_mzUQog03nAw=_PRY-uRjg@mail.gmail.com> (raw)
In-Reply-To: <20210414083820.GH4869@dell>
On Wed, Apr 14, 2021 at 3:38 AM Lee Jones <lee.jones@linaro.org> wrote:
>
> On Fri, 09 Apr 2021, satya priya wrote:
>
> > Convert pm8xxx bindings from .txt to .yaml format. Also,
> > split this binding into two: parent binding(qcom-pm8xxx.yaml)
> > and child node RTC binding(qcom-pm8xxx-rtc.yaml).
> >
> > Signed-off-by: satya priya <skakit@codeaurora.org>
> > ---
> > Changes in V2:
> > - As per Bjorn's comments, I've split this into two, one parent binding
> > and one child node rtc binding.
> > - Fixed bot errors and changed maintainer name.
> >
> > .../devicetree/bindings/mfd/qcom-pm8xxx.txt | 100 ---------------------
> > .../devicetree/bindings/mfd/qcom-pm8xxx.yaml | 54 +++++++++++
> > 2 files changed, 54 insertions(+), 100 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt
> > create mode 100644 Documentation/devicetree/bindings/mfd/qcom-pm8xxx.yaml
>
> Applied, thanks.
You need to apply the rtc schema too. linux-next has an error on this one now.
Rob
next prev parent reply other threads:[~2021-04-16 17:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:59 [PATCH V2 0/4] Add RTC support for PMIC PMK8350 satya priya
2021-04-09 13:59 ` [PATCH V2 1/4] rtc: pm8xxx: " satya priya
2021-04-09 13:59 ` [PATCH V2 2/4] dt-bindings: mfd: Add compatible for pmk8350 rtc satya priya
2021-04-12 18:20 ` Rob Herring
2021-04-14 8:37 ` Lee Jones
2021-04-09 13:59 ` [PATCH V2 3/4] dt-bindings: mfd: Convert pm8xxx bindings to yaml satya priya
2021-04-09 15:49 ` Bjorn Andersson
2021-04-10 14:47 ` kernel test robot
2021-04-10 14:47 ` kernel test robot
2021-04-12 18:21 ` Rob Herring
2021-04-14 8:38 ` Lee Jones
2021-04-16 17:20 ` Rob Herring [this message]
2021-04-16 19:17 ` Alexandre Belloni
2021-04-29 15:18 ` Rob Herring
2021-05-04 15:11 ` Alexandre Belloni
2021-04-09 13:59 ` [PATCH V2 4/4] dt-bindings: rtc: qcom-pm8xxx-rtc: Add qcom pm8xxx rtc bindings satya priya
2021-04-09 15:51 ` Bjorn Andersson
2021-04-11 12:35 ` kernel test robot
2021-04-11 12:35 ` kernel test robot
2021-04-12 18:21 ` Rob Herring
2021-04-13 18:32 ` [PATCH V2 0/4] Add RTC support for PMIC PMK8350 Alexandre Belloni
2021-04-16 22:20 ` (subset) " Alexandre Belloni
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm
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='CAL_JsqKYQ2EBgQJzKJSy-+D20Pmu_mzUQog03nAw=_PRY-uRjg@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=a.zummo@towertech.it \
--cc=agross@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kgunda@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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 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.