devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"dgdunix@gmail.com" <dgdunix@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH RESEND v6] Input: matrix-keypad - Add device tree support
Date: Tue, 20 Nov 2012 22:54:08 -0800	[thread overview]
Message-ID: <20121121065408.GB16772@core.coreip.homeip.net> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA77A5C@DBDE01.ent.ti.com>

On Wed, Nov 21, 2012 at 06:45:45AM +0000, AnilKumar, Chimata wrote:
> On Thu, Nov 15, 2012 at 19:43:08, AnilKumar, Chimata wrote:
> > Add device tree support to matrix keypad driver and usage details
> > are added to device tree documentation. Also modified the driver
> > according to recent update of matrix_keypad_build_keymap(), which
> > automatically allocate memory for keymap. Driver was tested on AM335x
> > EVM.
> > 
> > Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> > This patch was tested on AM335x-EVM and based on linux-next, cleanly
> > applies on top of "input/next"
> 
> Hi Dmity,
> 
> If there are no further comments on this patch, could you please
> take this in?

Applied to my 3.8 queue, thank you AnilKumar.

-- 
Dmitry

      reply	other threads:[~2012-11-21  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 14:13 [PATCH RESEND v6] Input: matrix-keypad - Add device tree support AnilKumar Ch
2012-11-21  6:45 ` AnilKumar, Chimata
2012-11-21  6:54   ` 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=20121121065408.GB16772@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=anilkumar@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dgdunix@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-input@vger.kernel.org \
    --cc=rob.herring@calxeda.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).