From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Patil, Rachna" <rachna@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-iio@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
Jonathan Cameron <jic23@cam.ac.uk>
Subject: Re: [PATCH RESEND 0/8] TI Touchscreen driver updates and Support for TSC/ADC MFD driver
Date: Tue, 16 Oct 2012 10:42:07 -0700 [thread overview]
Message-ID: <20121016174207.GA1833@core.coreip.homeip.net> (raw)
In-Reply-To: <1350372345-27108-1-git-send-email-rachna@ti.com>
Hi Rachna,
On Tue, Oct 16, 2012 at 12:55:37PM +0530, Patil, Rachna wrote:
> This patch set is a cumulative set of [1] and [2] sent earlier.
> I have merged the patch set so that the MFD patches apply without
> any issues.
>
> Also Note that there are no code changes in either of the patch set,
> only rebased on top of linux-next to make sure that all the patches
> apply without any conflicts.
>
> This patch set has been tested on AM335x EVM.
>
> [1] "[PATCH 0/4] input: TSC: ti_tscadc: TI Touchscreen driver updates"
> (http://www.spinics.net/lists/linux-input/msg22107.html)
>
> [2] "[PATCH v5 0/4] Support for TSC/ADC MFD driver"
> (http://www.spinics.net/lists/linux-input/msg22832.html)
>
> Patil, Rachna (8):
> input: TSC: ti_tscadc: Correct register usage
> input: TSC: ti_tscadc: Add Step configuration as platform data
> input: TSC: ti_tscadc: set FIFO0 threshold Interrupt
> input: TSC: ti_tscadc: Remove definition of End Of Interrupt register
> input: TSC: ti_tscadc: Rename the existing touchscreen driver
> MFD: ti_tscadc: Add support for TI's TSC/ADC MFDevice
> input: TSC: ti_tsc: Convert TSC into a MFDevice
> IIO : ADC: tiadc: Add support of TI's ADC driver
I am fine with input portion of the patch series, please merge through
MFD tree.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-10-16 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:25 [PATCH RESEND 0/8] TI Touchscreen driver updates and Support for TSC/ADC MFD driver Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 1/8] input: TSC: ti_tscadc: Correct register usage Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 2/8] input: TSC: ti_tscadc: Add Step configuration as platform data Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 3/8] input: TSC: ti_tscadc: set FIFO0 threshold Interrupt Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 4/8] input: TSC: ti_tscadc: Remove definition of End Of Interrupt register Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 5/8] input: TSC: ti_tscadc: Rename the existing touchscreen driver Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 6/8] MFD: ti_tscadc: Add support for TI's TSC/ADC MFDevice Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 7/8] input: TSC: ti_tsc: Convert TSC into a MFDevice Patil, Rachna
2012-10-16 7:25 ` [PATCH RESEND 8/8] IIO : ADC: tiadc: Add support of TI's ADC driver Patil, Rachna
2012-10-16 17:42 ` Dmitry Torokhov [this message]
2012-10-17 6:11 ` [PATCH RESEND 0/8] TI Touchscreen driver updates and Support for TSC/ADC MFD driver Patil, Rachna
2012-10-29 7:13 ` Patil, Rachna
2012-10-22 10:46 ` Patil, Rachna
2012-11-05 22:55 ` Samuel Ortiz
2012-11-06 4:47 ` Patil, Rachna
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=20121016174207.GA1833@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rachna@ti.com \
--cc=sameo@linux.intel.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).