From: Benoit Cousson <b-cousson@ti.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] ARM: DTS: OMAP4: Panda/SDP: twl6030: fix mux for IRQ pin and msecure line
Date: Wed, 29 May 2013 18:48:12 +0200 [thread overview]
Message-ID: <51A6314C.1080803@ti.com> (raw)
In-Reply-To: <87li6x9325.fsf@linaro.org>
On 05/29/2013 06:13 PM, Kevin Hilman wrote:
> "Cousson, Benoit" <b-cousson@ti.com> writes:
>
>> On 5/29/2013 5:29 PM, Kevin Hilman wrote:
>>>
>>> On May 29, 2013 8:06 AM, "Cousson, Benoit" <b-cousson@ti.com
>>> <mailto:b-cousson@ti.com>> wrote:
>>> >
>>> > On 5/29/2013 4:03 PM, Kevin Hilman wrote:
>>> >>
>>> >> "Cousson, Benoit" <b-cousson@ti.com <mailto:b-cousson@ti.com>> writes:
>>> >>
>>> >> [...]
>>> >>
>>> >>>>
>>> >>>> Let me respin this after some more doc reading.
>>> >>>
>>> >>>
>>> >>> Did you re-spin it already?
>>> >>
>>> >>
>>> >> Yes, v2 is here.
>>> >>
>>> >> http://marc.info/?l=linux-omap&m=136944147521955&w=2
>>> >>
>>> >> It also needed a rework because the fref_clk0_out pin is also in the
>>> >> wkup section of the padconf, not core.
>>> >
>>> >
>>> > OK, I'll wait for the v3 then :-)
>>> >
>>>
>>> Hmm, why? v2 has the wkup changes included.
>>
>> Why? Because of my bad understanding of English :-)
>> I understood: It also needs a rework...
>
> Re-reading, I wasn't terribly clear. Sorry for the confusion.
>
>> Sorry, I'll merge it.
>
> I was hoping for an Ack from Nishanth since he had some questions about
> it, but with the double checking from you and Grygorii, I think it
> should go in for the -rc cycle. (also, please add an Ack from Grygorii.)
OK, I'll push the fix to Tony ASAP.
Thanks,
Benoit
prev parent reply other threads:[~2013-05-29 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 19:28 [PATCH] ARM: DTS: OMAP4: Panda/SDP: twl6030: fix mux for IRQ pin and msecure line Kevin Hilman
2013-05-24 20:09 ` Nishanth Menon
2013-05-24 20:32 ` Nishanth Menon
2013-05-24 21:19 ` Kevin Hilman
2013-05-24 21:25 ` Nishanth Menon
2013-05-24 21:51 ` Kevin Hilman
2013-05-24 22:15 ` Kevin Hilman
2013-05-26 17:35 ` Nishanth Menon
2013-05-28 18:33 ` Kevin Hilman
2013-05-29 8:36 ` Grygorii Strashko
2013-05-29 16:12 ` Kevin Hilman
2013-05-29 9:36 ` Cousson, Benoit
2013-05-29 9:38 ` Cousson, Benoit
2013-05-29 14:03 ` Kevin Hilman
2013-05-29 14:23 ` Cousson, Benoit
[not found] ` <CAGa+x85ZzfX400eEGmTGPzRiC21S83VRiHYj38cqsJLjDF3L7g@mail.gmail.com>
2013-05-29 16:02 ` Cousson, Benoit
2013-05-29 16:13 ` Kevin Hilman
2013-05-29 16:48 ` Benoit Cousson [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=51A6314C.1080803@ti.com \
--to=b-cousson@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.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).