devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: dmitry.torokhov@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, raphaelpereira@gmail.com,
	voice.shen@atmel.com, linux-input@vger.kernel.org,
	kernel@pengutronix.de
Subject: [PATCH v2 0/2] Microchip QT1050 support
Date: Mon, 29 Oct 2018 14:38:24 +0100	[thread overview]
Message-ID: <20181029133826.30326-1-m.felsch@pengutronix.de> (raw)

Hi,

this is my v2 containing the comments made on my v1 [1].

I split the dt-bindings according to commit [2].

[1] https://www.spinics.net/lists/devicetree/msg250279.html
[2] https://www.spinics.net/lists/devicetree/msg253946.html

Marco Felsch (2):
  dt-bindings: input: add Microchip QT1050 bindings
  Input: qt1050 - add Microchip AT42QT1050 support

 .../bindings/input/microchip,qt1050.txt       |  74 +++
 drivers/input/keyboard/Kconfig                |  11 +
 drivers/input/keyboard/Makefile               |   1 +
 drivers/input/keyboard/qt1050.c               | 620 ++++++++++++++++++
 4 files changed, 706 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/input/microchip,qt1050.txt
 create mode 100644 drivers/input/keyboard/qt1050.c

-- 
2.19.1

             reply	other threads:[~2018-10-29 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 13:38 Marco Felsch [this message]
2018-10-29 13:38 ` [PATCH v2 1/2] dt-bindings: input: add Microchip QT1050 bindings Marco Felsch
2018-10-30 22:26   ` Rob Herring
2018-10-29 13:38 ` [PATCH v2 2/2] Input: qt1050 - add Microchip AT42QT1050 support Marco Felsch
2019-01-17  7:59   ` Dmitry Torokhov
2019-03-06 10:19     ` Marco Felsch
2018-11-26  9:13 ` [PATCH v2 0/2] Microchip QT1050 support Marco Felsch
2019-01-15 11:58   ` Marco Felsch

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=20181029133826.30326-1-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-input@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=raphaelpereira@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=voice.shen@atmel.com \
    /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).