All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Stephen Warren <swarren@nvidia.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V4 0/4] input: keyboard: tegra: cleanups and DT supports
Date: Fri, 11 Jan 2013 10:17:34 +0530	[thread overview]
Message-ID: <50EF9966.1010500@nvidia.com> (raw)
In-Reply-To: <20130110174456.GA2797@core.coreip.homeip.net>

On Thursday 10 January 2013 11:14 PM, Dmitry Torokhov wrote:
> Hi Laxman,
>
> On Thu, Jan 10, 2013 at 12:01:23PM +0530, Laxman Dewangan wrote:
>> Hi Dmitry,
>>
>> On Monday 07 January 2013 10:22 PM, Stephen Warren wrote:
>>> 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>
>>>
>> If you are fine with this series then can it be apply please? I can
>> handle if there is any comment on this series to close this.
>>
> The patches are applied with minor edits to the 3rd and 4th (there was
> no point in having a separate keymap setup function anymore).
>

Thanks for taking care. I looked the final change from your git and the 
changes are  fine.
Thanks,
Laxman

      reply	other threads:[~2013-01-11  4:47 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 ` [PATCH V4 0/4] input: keyboard: tegra: cleanups and DT supports Stephen Warren
2013-01-10  6:31   ` Laxman Dewangan
2013-01-10 17:44     ` Dmitry Torokhov
2013-01-11  4:47       ` Laxman Dewangan [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=50EF9966.1010500@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.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 \
    --cc=swarren@wwwdotorg.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 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.