From: Sekhar Nori <nsekhar@ti.com>
To: Sushaanth Srirangapathi <sushaanth.s@ti.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Joe Perches <joe@perches.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: DTS: da850: add DT node for tps6507x-ts
Date: Wed, 17 Feb 2016 18:56:07 +0530 [thread overview]
Message-ID: <56C474EF.5040006@ti.com> (raw)
In-Reply-To: <1454308130-12452-5-git-send-email-sushaanth.s@ti.com>
On Monday 01 February 2016 11:58 AM, Sushaanth Srirangapathi wrote:
> add tps6507x touchscreen device tree node information to
> DA850 EVM
>
> Signed-off-by: Sushaanth Srirangapathi <sushaanth.s@ti.com>
Acked-by: Sekhar Nori <nsekhar@ti.com>
I can queue 3/3 once driver changes are accepted (let me know about that
because I am not copied on this series).
If Dmitry wants to queue the whole series once he has had a look, thats
fine too. I have nothing that will clash with this.
Regards,
Sekhar
next prev parent reply other threads:[~2016-02-17 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 6:28 [PATCH 0/3] Add Device Tree support for tps6507x-ts Sushaanth Srirangapathi
2016-02-01 6:28 ` [PATCH 1/3] Input: tps6507x-ts - add binding " Sushaanth Srirangapathi
2016-02-01 14:39 ` Rob Herring
2016-02-01 6:28 ` [PATCH 1/3] Input: tps6507x-ts - add support " Sushaanth Srirangapathi
2016-02-01 6:42 ` Sushaanth Srirangapathi
2016-02-01 6:28 ` [PATCH 2/3] Input: tps6507x-ts - Add device tree support Sushaanth Srirangapathi
2016-02-01 6:28 ` [PATCH 3/3] ARM: DTS: da850: add DT node for tps6507x-ts Sushaanth Srirangapathi
2016-02-17 13:26 ` Sekhar Nori [this message]
2016-04-07 9:36 ` Sekhar Nori
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=56C474EF.5040006@ti.com \
--to=nsekhar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier@osg.samsung.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sushaanth.s@ti.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).