From: kiran.padwal@smartplayin.com
To: "Kumar Gala" <galak@codeaurora.org>
Cc: "Andy Gross" <agross@codeaurora.org>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, davidb@codeaurora.org,
afaerber@suse.de, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ARM: apq8064: Add pinmux and i2c pinctrl nodes
Date: Wed, 17 Sep 2014 06:26:44 -0400 (EDT) [thread overview]
Message-ID: <1410949604.906729871@apps.rackspace.com> (raw)
In-Reply-To: <96034F94-3C6D-43FC-95EF-7FA705724F99@codeaurora.org>
On Tuesday, September 16, 2014 3:00pm, "Kumar Gala" <galak@codeaurora.org> said:
>
> On Sep 16, 2014, at 5:36 AM, kiran.padwal@smartplayin.com wrote:
>
>>
>>
>> On Monday, September 15, 2014 10:39pm, "Andy Gross" <agross@codeaurora.org>
>> said:
>>
>>> On Tue, Aug 26, 2014 at 05:00:45PM +0530, Kiran Padwal wrote:
>>>> This patch adds pinmux and i2c pinctrl DT node for IFC6410 board.
>>>> It also adds necessary DT support for i2c eeprom which is present on
>>>> IFC6410.
>>>>
>>>> Tested on IFC6410 board.
>>>
>>> Looks fine
>>
>> Thanks for review.
>
> Can you rebase this on:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
> tags/qcom-dt-for-3.18
Sure, I will resend this patch gain.
>
> - k
>
> --
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The
> Linux Foundation
>
>
prev parent reply other threads:[~2014-09-17 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 11:30 [PATCH v3] ARM: apq8064: Add pinmux and i2c pinctrl nodes Kiran Padwal
2014-09-16 2:39 ` Andy Gross
2014-09-16 12:36 ` kiran.padwal
2014-09-16 19:00 ` Kumar Gala
2014-09-17 10:26 ` kiran.padwal [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=1410949604.906729871@apps.rackspace.com \
--to=kiran.padwal@smartplayin.com \
--cc=afaerber@suse.de \
--cc=agross@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@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 \
/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