linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: Linux-imx@nxp.com, shawnguo@kernel.org, robh+dt@kernel.org,
	linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
	s.hauer@pengutronix.de, olof@lixom.net, kernel@pengutronix.de,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	gnuiyl@gmail.com, linux-arm-kernel@lists.infradead.org,
	festevam@gmail.com
Subject: Re: [PATCH V2 2/2] dt-bindings: input: Convert imx keypad to json-schema
Date: Thu, 9 Jul 2020 17:28:29 -0600	[thread overview]
Message-ID: <20200709232829.GA1099006@bogus> (raw)
In-Reply-To: <1592285467-18371-2-git-send-email-Anson.Huang@nxp.com>

On Tue, 16 Jun 2020 13:31:07 +0800, Anson Huang wrote:
> Convert the i.MX KEYPAD binding to DT schema format using json-schema
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> Changes since V1:
> 	- include matrix-keymap.yaml and "linux,keymap" is unnecessary now, remove it.
> ---
>  .../devicetree/bindings/input/imx-keypad.txt       | 53 --------------
>  .../devicetree/bindings/input/imx-keypad.yaml      | 85 ++++++++++++++++++++++
>  2 files changed, 85 insertions(+), 53 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/input/imx-keypad.txt
>  create mode 100644 Documentation/devicetree/bindings/input/imx-keypad.yaml
> 

Applied, thanks!

  reply	other threads:[~2020-07-09 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  5:31 [PATCH V2 1/2] dt-bindings: input: Convert matrix-keymap to json-schema Anson Huang
2020-06-16  5:31 ` [PATCH V2 2/2] dt-bindings: input: Convert imx keypad " Anson Huang
2020-07-09 23:28   ` Rob Herring [this message]
2020-07-09 23:28 ` [PATCH V2 1/2] dt-bindings: input: Convert matrix-keymap " 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=20200709232829.GA1099006@bogus \
    --to=robh@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=Linux-imx@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=festevam@gmail.com \
    --cc=gnuiyl@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).