From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Benjamin Gaignard <benjamin.gaignard@st.com>,
robh+dt@kernel.org, mark.rutland@arm.com, megous@megous.com,
mylene.josserand@bootlin.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: touchscreen: Convert edt-ft5x06 to json-schema
Date: Thu, 6 Feb 2020 16:19:46 -0800 [thread overview]
Message-ID: <20200207001946.GI184237@dtor-ws> (raw)
In-Reply-To: <20200206215322.GA12956@bogus>
On Thu, Feb 06, 2020 at 02:53:22PM -0700, Rob Herring wrote:
> On Thu, 6 Feb 2020 11:14:34 +0100, Benjamin Gaignard wrote:
> > Convert the EDT-FT5x06 to DT schema using json-schema.
> >
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> > ---
> > version 2:
> > - preserve formatting in description
> > - use 'const' rather than 'enum' for reg property
> > - fix max/min issues
> > .../bindings/input/touchscreen/edt-ft5x06.txt | 75 -------------
> > .../bindings/input/touchscreen/edt-ft5x06.yaml | 123 +++++++++++++++++++++
> > 2 files changed, 123 insertions(+), 75 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt
> > create mode 100644 Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Unfortunately this does not apply as the latest binding was extended to
document "wakeup-source" property. Could you please refresh against
mainline or my tree?
Thanks.
--
Dmitry
prev parent reply other threads:[~2020-02-07 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 10:14 [PATCH v2] dt-bindings: touchscreen: Convert edt-ft5x06 to json-schema Benjamin Gaignard
2020-02-06 21:53 ` Rob Herring
2020-02-07 0:19 ` Dmitry Torokhov [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=20200207001946.GI184237@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=megous@megous.com \
--cc=mylene.josserand@bootlin.com \
--cc=robh+dt@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).