mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: dmitry.torokhov@gmail.com, axel.lin@gmail.com, riyer@nvidia.com,
	michael.hennerich@analog.com, grant.likely@secretlab.ca,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kevin.wells@nxp.com,
	srinivas.bakki@nxp.com, devicetree-discuss@lists.ozlabs.org,
	rob.herring@calxeda.com
Subject: [GIT PULL] input: keyboard: Add keys driver for the LPC32xx SoC
Date: Sat, 05 May 2012 14:09:46 +0200	[thread overview]
Message-ID: <4FA5188A.1090401@antcom.de> (raw)

Hi,

this is the pull request for the LPC32xx keys driver, built on top of
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git - branch "next"

Thanks in advance,

Roland


The following changes since commit 2872a9b521ac936c7a8525a8c2bdfb9b4ccf5cfc:

  Input: evdev - properly handle read/write with count 0 (2012-05-02 00:23:58 -0700)

are available in the git repository at:

  git://git.antcom.de/linux-2.6.git lpc32xx-keys

for you to fetch changes up to 0c98c603ef48859d887f6fee1d5b18481219d6ea:

  input: keyboard: Add keys driver for the LPC32xx SoC (2012-05-05 13:53:16 +0200)

----------------------------------------------------------------
Roland Stigge (1):
      input: keyboard: Add keys driver for the LPC32xx SoC

 .../devicetree/bindings/input/lpc32xx-key.txt      |   28 ++
 drivers/input/keyboard/Kconfig                     |   10 +
 drivers/input/keyboard/Makefile                    |    1 +
 drivers/input/keyboard/lpc32xx-keys.c              |  382 ++++++++++++++++++++
 4 files changed, 421 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/input/lpc32xx-key.txt
 create mode 100644 drivers/input/keyboard/lpc32xx-keys.c

                 reply	other threads:[~2012-05-05 12:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FA5188A.1090401@antcom.de \
    --to=stigge@antcom.de \
    --cc=axel.lin@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=kevin.wells@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=riyer@nvidia.com \
    --cc=rob.herring@calxeda.com \
    --cc=srinivas.bakki@nxp.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

Powered by JetHome