From: Robert Marko <robimarko@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-i2c@vger.kernel.org,
Devicetree List <devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: i2c: qcom,i2c-qup: convert to dtschema
Date: Sun, 5 Jun 2022 18:09:10 +0200 [thread overview]
Message-ID: <CAOX2RU7PHpzKUNvuv=-MyqGtgcz30qKkvx2MHNV=ehtCZGBYEA@mail.gmail.com> (raw)
In-Reply-To: <20220605140744.GA3416078-robh@kernel.org>
On Sun, 5 Jun 2022 at 16:07, Rob Herring <robh@kernel.org> wrote:
>
> On Sat, Jun 04, 2022 at 06:46:53PM +0200, Robert Marko wrote:
> > Convert DT bindings for Qualcomm QUP I2C controller to DT schema format.
> >
> > Old text bindings were missing usage of DMA so that was documented, as
> > well as the max clock-frequency.
> >
> > Signed-off-by: Robert Marko <robimarko@gmail.com>
> > ---
> > .../devicetree/bindings/i2c/qcom,i2c-qup.txt | 40 ---------
> > .../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 83 +++++++++++++++++++
> > 2 files changed, 83 insertions(+), 40 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-qup.txt
> > create mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-qup.yaml
>
> This one is already done.
Yeah, I did not check linux-next before doing the conversion.
Sorry for the noise.
Regards,
Robert
>
> Rob
next prev parent reply other threads:[~2022-06-05 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 16:46 [PATCH] dt-bindings: i2c: qcom,i2c-qup: convert to dtschema Robert Marko
2022-06-05 2:17 ` Rob Herring
2022-06-05 14:07 ` Rob Herring
2022-06-05 16:09 ` Robert Marko [this message]
2022-06-06 7:26 ` Krzysztof Kozlowski
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='CAOX2RU7PHpzKUNvuv=-MyqGtgcz30qKkvx2MHNV=ehtCZGBYEA@mail.gmail.com' \
--to=robimarko@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).