linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, avictor.za@gmail.com
Cc: linux-input@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] input: atmel_tsadcc: touchscreen rework setting	capabilities
Date: Thu, 19 Nov 2009 11:47:39 +0100	[thread overview]
Message-ID: <4B05224B.8050403@atmel.com> (raw)
In-Reply-To: <20091118173033.GA4385@core.coreip.homeip.net>

Dmitry Torokhov :
> Hi Nicolas,
> 
> On Wed, Nov 18, 2009 at 03:12:12PM +0100, Nicolas Ferre wrote:
>> Tiny patch for setting capabilities using input API function.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> 
> All looks good. Since the series span platform and input subtrees how do
> you want to merge it?

I propose that you merge the whole series using the input path.

I had the acknowledgment from Andrew Victor offline. So, could you
please add on patches #3 & #4:

Acked-by: Andrew Victor <linux@maxim.org.za>

Thanks a lot.

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2009-11-19 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 14:12 [PATCH 1/4] input: atmel_tsadcc: touchscreen rework setting capabilities Nicolas Ferre
2009-11-18 14:12 ` [PATCH 2/4] input: atmel_tsadcc touchscreen use platform parameters Nicolas Ferre
2009-11-18 14:12 ` [PATCH 3/4] at91/input: platform parameters for atmel_tsadcc in at91sam9rlek Nicolas Ferre
2009-11-18 14:12 ` [PATCH 4/4] at91/input: touchscreen support for at91sam9g45ekes Nicolas Ferre
2009-11-18 17:30 ` [PATCH 1/4] input: atmel_tsadcc: touchscreen rework setting capabilities Dmitry Torokhov
2009-11-19 10:47   ` Nicolas Ferre [this message]
2009-11-19 17:04     ` Dmitry Torokhov

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=4B05224B.8050403@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=avictor.za@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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).