From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v1 1/5] dt-bindings: i2c: convert rockchip i2c bindings to yaml
Date: Thu, 12 Mar 2020 10:50:44 -0500 [thread overview]
Message-ID: <20200312155044.GA25292@bogus> (raw)
In-Reply-To: <20200305143611.10733-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, 5 Mar 2020 15:36:07 +0100, Johan Jonker wrote:
> Current dts files with 'i2c' nodes are manually verified.
> In order to automate this process i2c-rk3x.txt
> has to be converted to yaml. In the new setup
> i2c-rk3x.yaml will inherit properties from
> i2c-controller.yaml.
>
> Also change document name in MAINTAINERS.
>
> Signed-off-by: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 68 -----------
> .../devicetree/bindings/i2c/i2c-rk3x.yaml | 129 +++++++++++++++++++++
> MAINTAINERS | 2 +-
> 3 files changed, 130 insertions(+), 69 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-rk3x.yaml
>
Reviewed-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
next prev parent reply other threads:[~2020-03-12 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 14:36 [PATCH v1 1/5] dt-bindings: i2c: convert rockchip i2c bindings to yaml Johan Jonker
2020-03-05 14:36 ` [PATCH v1 2/5] dt-bindings: i2c: i2c-rk3x: add description for rk3036 Johan Jonker
[not found] ` <20200305143611.10733-2-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-12 15:51 ` Rob Herring
2020-03-05 14:36 ` [PATCH v1 3/5] dt-bindings: i2c: i2c-rk3x: add description for rk3368 Johan Jonker
2020-03-12 15:51 ` Rob Herring
2020-03-05 14:36 ` [PATCH v1 4/5] dt-bindings: i2c: i2c-rk3x: add description for rk3308 Johan Jonker
[not found] ` <20200305143611.10733-4-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-12 15:52 ` Rob Herring
[not found] ` <20200305143611.10733-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-05 14:36 ` [PATCH v1 5/5] dt-bindings: i2c: i2c-rk3x: add description for px30 Johan Jonker
2020-03-12 15:50 ` Rob Herring [this message]
2020-03-12 15:54 ` [PATCH v1 1/5] dt-bindings: i2c: convert rockchip i2c bindings to yaml Rob Herring
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=20200312155044.GA25292@bogus \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).