From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: dmitry.torokhov@gmail.com, swarren@nvidia.com,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
linux-input@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V4 0/4] input: keyboard: tegra: cleanups and DT supports
Date: Mon, 07 Jan 2013 09:52:06 -0700 [thread overview]
Message-ID: <50EAFD36.9070909@wwwdotorg.org> (raw)
In-Reply-To: <1357470900-12619-1-git-send-email-ldewangan@nvidia.com>
On 01/06/2013 04:14 AM, Laxman Dewangan wrote:
> This patch series:
> - fix build warning,
> - use devm_* for allocation,
> - make column/rows configuration through DT and
> - remove the rarely used key mapping table.
The series,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-01-07 16:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 11:14 [PATCH V4 0/4] input: keyboard: tegra: cleanups and DT supports Laxman Dewangan
2013-01-06 11:14 ` Laxman Dewangan
[not found] ` <1357470900-12619-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-06 11:14 ` [PATCH V4 1/4] input: keyboard: tegra: fix build warning Laxman Dewangan
2013-01-06 11:14 ` Laxman Dewangan
2013-01-06 11:14 ` [PATCH V4 2/4] input: keyboard: tegra: use devm_* for resource allocation Laxman Dewangan
2013-01-06 11:14 ` Laxman Dewangan
2013-01-06 11:14 ` [PATCH V4 3/4] input: keyboard: tegra: add support for rows/cols configuration from dt Laxman Dewangan
2013-01-06 11:14 ` Laxman Dewangan
2013-02-11 21:36 ` Grant Likely
2013-02-11 21:36 ` Grant Likely
2013-01-06 11:15 ` [PATCH V4 4/4] input: keyboard: tegra: remove default key mapping Laxman Dewangan
2013-01-06 11:15 ` Laxman Dewangan
2013-01-07 16:52 ` Stephen Warren [this message]
2013-01-10 6:31 ` [PATCH V4 0/4] input: keyboard: tegra: cleanups and DT supports Laxman Dewangan
2013-01-10 17:44 ` Dmitry Torokhov
2013-01-11 4:47 ` Laxman Dewangan
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=50EAFD36.9070909@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.