linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux@arm.linux.org.uk, b-cousson@ti.com,
	rob.herring@calxeda.com, grant.likely@secretlab.ca,
	tony@atomide.com, rnayak@ti.com, hvaibhav@ti.com,
	peter.ujfalusi@ti.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, balbi@ti.com
Subject: Re: [PATCH 0/4] arm/dts: omap: add dt data for MUSB
Date: Thu, 6 Sep 2012 16:22:24 +0300	[thread overview]
Message-ID: <20120906132223.GL29202@arwen.pp.htv.fi> (raw)
In-Reply-To: <1344259395-4559-1-git-send-email-kishon@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

Hi,

On Mon, Aug 06, 2012 at 06:53:11PM +0530, Kishon Vijay Abraham I wrote:
> This patch series adds dt data for MUSB and related modules to
> get MUSB working
> 
> These patches were initially part of
> [PATCH v6 00/11] omap: musb: Add device tree support
> 
> These patches can be tested by applying it over
> [PATCH v7 0/7] omap: musb: Add device tree support
> 
> These patches were developed on
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> 
> If it needs to be rebased on some other tree, pls let me
> know.
> 
> Performed MUSB device mode testing on omap4 panda,
> omap4 sdp and omap3 beagle

Grant, we already lost two merge windows on this patchset. Is it
possible for you to take a look here so we don't loose another merge
window ? Can Benoit just take these patches on his tree, so it goes
upstream through the linux-omap tree ?

cheers

> Kishon Vijay Abraham I (4):
>   arm/dts: omap: Add omap-usb2 dt data
>   arm/dts: Add twl6030-usb data
>   arm/dts: Add twl4030-usb data
>   arm/dts: omap: Add usb_otg and glue data
> 
>  arch/arm/boot/dts/omap3-beagle.dts |    6 ++++++
>  arch/arm/boot/dts/omap3-evm.dts    |    6 ++++++
>  arch/arm/boot/dts/omap3.dtsi       |    8 ++++++++
>  arch/arm/boot/dts/omap4-panda.dts  |   10 ++++++++++
>  arch/arm/boot/dts/omap4-sdp.dts    |   10 ++++++++++
>  arch/arm/boot/dts/omap4.dtsi       |   13 +++++++++++++
>  arch/arm/boot/dts/twl4030.dtsi     |   21 +++++++++++++++++++++
>  arch/arm/boot/dts/twl6030.dtsi     |    5 +++++
>  8 files changed, 79 insertions(+)
> 
> -- 
> 1.7.9.5
> 

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2012-09-06 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 13:23 [PATCH 0/4] arm/dts: omap: add dt data for MUSB Kishon Vijay Abraham I
2012-08-06 13:23 ` [PATCH 1/4] arm/dts: omap: Add omap-usb2 dt data Kishon Vijay Abraham I
2012-08-06 13:23 ` [PATCH 2/4] arm/dts: Add twl6030-usb data Kishon Vijay Abraham I
2012-08-06 13:23 ` [PATCH 3/4] arm/dts: Add twl4030-usb data Kishon Vijay Abraham I
2012-08-06 13:23 ` [PATCH 4/4] arm/dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
2012-09-06 13:22 ` Felipe Balbi [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=20120906132223.GL29202@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=grant.likely@secretlab.ca \
    --cc=hvaibhav@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=rnayak@ti.com \
    --cc=rob.herring@calxeda.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).