From: kishon <kishon@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, tony@atomide.com, linux@arm.linux.org.uk,
balbi@ti.com, gregkh@linuxfoundation.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 0/3] ARM: dts: omap: add dt data for MUSB
Date: Thu, 10 Jan 2013 16:23:11 +0530 [thread overview]
Message-ID: <50EE9D97.6000803@ti.com> (raw)
In-Reply-To: <50EE90B6.2060308@ti.com>
Hi,
On Thursday 10 January 2013 03:28 PM, Benoit Cousson wrote:
> Hi Kishon,
>
> On 01/10/2013 07:19 AM, kishon wrote:
>> On Friday 28 December 2012 12:05 AM, Aaro Koskinen wrote:
>>> Hi,
>>>
>>> On Thu, Sep 20, 2012 at 05:21:15AM +0200, Benoit Cousson wrote:
>>>> On 09/19/2012 11:32 AM, Kishon Vijay Abraham I wrote:
>>>>> This patch series adds dt data to get MUSB working in omap4 and omap3
>>>>>
>>>>> Changes from v2:
>>>>> * Changes the subject of all the patches to include "ARM: dts:"
>>>>> * Added reg property and interrupt property for "usb_otg_hs".
>>>>> Previously these
>>>>> were obtained from ti,hwmods property.
>>>>> * Rebased on
>>>>>
>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
>>>>> devel-dt
>>>>>
>>>>> Changes from v1:
>>>>> Just removed the omap-usb2 dt data and sent that as a separate patch.
>>>>>
>>>>> Kishon Vijay Abraham I (3):
>>>>> ARM: dts: Add twl6030-usb data
>>>>> ARM: dts: Add twl4030-usb data
>>>>> ARM: dts: omap: Add usb_otg and glue data
>>>>
>>>> Thanks for the update. I've just pulled the series for 3.7.
>>>
>>> I wonder what happened to the patch #3 (Add usb_otg and glue data)
>>> of this series? Why was it dropped? I cannot see it in 3.7 or 3.8-rc1.
>
> I don't remember the context, can you repost it rebased on 3.8-rc2? Did
> it generate some discussion at that time?
That patch also has SCM register. It might be rejected because of that.
Will work on the that.
Thanks
Kishon
next prev parent reply other threads:[~2013-01-10 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 9:32 [PATCH v3 0/3] ARM: dts: omap: add dt data for MUSB Kishon Vijay Abraham I
2012-09-19 9:32 ` [PATCH v3 1/3] ARM: dts: Add twl6030-usb data Kishon Vijay Abraham I
2012-09-19 9:32 ` [PATCH v3 2/3] ARM: dts: Add twl4030-usb data Kishon Vijay Abraham I
2012-09-19 9:32 ` [PATCH v3 3/3] ARM: dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
[not found] ` <1348047128-25692-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2012-09-20 3:21 ` [PATCH v3 0/3] ARM: dts: omap: add dt data for MUSB Benoit Cousson
2012-12-27 18:35 ` Aaro Koskinen
[not found] ` <20121227183524.GB7097-R3WNPi76c83LsdW6vOPryG4HOFkwEHDbMR2xtNvyitY@public.gmane.org>
2013-01-10 6:19 ` kishon
2013-01-10 9:58 ` Benoit Cousson
2013-01-10 10:53 ` kishon [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 10:26 Kishon Vijay Abraham I
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=50EE9D97.6000803@ti.com \
--to=kishon@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--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).