All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, bcousson@baylibre.com,
	linux-usb@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
	broonie@kernel.org, p.zabel@pengutronix.de,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH v2 3/9] ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct usbhs_phy_data
Date: Fri, 20 Sep 2013 11:24:19 -0500	[thread overview]
Message-ID: <20130920162419.GD18721@radagast> (raw)
In-Reply-To: <20130920161822.GR9994@atomide.com>


[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]

On Fri, Sep 20, 2013 at 09:18:22AM -0700, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [130920 08:52]:
> > Hi,
> > 
> > On Thu, Aug 15, 2013 at 01:18:23PM +0300, Roger Quadros wrote:
> > > The platform data bits can be inferred from the other members of
> > > struct usbhs_phy_data. So get rid of the platform_data member.
> > > 
> > > Build the platform data for the PHY device in usbhs_init_phys() instead.
> > > 
> > > Signed-off-by: Roger Quadros <rogerq@ti.com>
> > 
> > Tony, do I get your Acked-by here and all following arch/arm/mach-omap2*
> > patches in this series ?
> 
> If you can merge just this series without the .dts changes
> into an immutable topic branch against let's say v3.12-rc2
> when it comes out, then yes I can ack them:
> 
> Acked-by: Tony Lindgren <tony@atomide.com>
> 
> That way I can also pull in the topic branch as needed to
> avoid self inflicted merge conflicts ;) And Benoit can
> set up a separate .dts branch based on your branch to make
> sure the dependencies are in place before merging that one
> upstream.

Alright, i'll put this in my todo for next week.

-- 
balbi

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/9] ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct usbhs_phy_data
Date: Fri, 20 Sep 2013 11:24:19 -0500	[thread overview]
Message-ID: <20130920162419.GD18721@radagast> (raw)
In-Reply-To: <20130920161822.GR9994@atomide.com>

On Fri, Sep 20, 2013 at 09:18:22AM -0700, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [130920 08:52]:
> > Hi,
> > 
> > On Thu, Aug 15, 2013 at 01:18:23PM +0300, Roger Quadros wrote:
> > > The platform data bits can be inferred from the other members of
> > > struct usbhs_phy_data. So get rid of the platform_data member.
> > > 
> > > Build the platform data for the PHY device in usbhs_init_phys() instead.
> > > 
> > > Signed-off-by: Roger Quadros <rogerq@ti.com>
> > 
> > Tony, do I get your Acked-by here and all following arch/arm/mach-omap2*
> > patches in this series ?
> 
> If you can merge just this series without the .dts changes
> into an immutable topic branch against let's say v3.12-rc2
> when it comes out, then yes I can ack them:
> 
> Acked-by: Tony Lindgren <tony@atomide.com>
> 
> That way I can also pull in the topic branch as needed to
> avoid self inflicted merge conflicts ;) And Benoit can
> set up a separate .dts branch based on your branch to make
> sure the dependencies are in place before merging that one
> upstream.

Alright, i'll put this in my todo for next week.

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130920/aac5c4d4/attachment.sig>

  reply	other threads:[~2013-09-20 16:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 10:18 [PATCH v2 0/9] USB: phy: phy-nop: Manage RESET GPIO in the driver Roger Quadros
2013-08-15 10:18 ` Roger Quadros
     [not found] ` <1376561909-4406-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-08-15 10:18   ` [PATCH v2 1/9] usb: phy: nop: Add gpio_reset to platform data Roger Quadros
2013-08-15 10:18     ` Roger Quadros
2013-08-15 10:18   ` [PATCH v2 3/9] ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct usbhs_phy_data Roger Quadros
2013-08-15 10:18     ` Roger Quadros
2013-09-20 15:44     ` Felipe Balbi
2013-09-20 15:44       ` Felipe Balbi
2013-09-20 16:18       ` Tony Lindgren
2013-09-20 16:18         ` Tony Lindgren
2013-09-20 16:24         ` Felipe Balbi [this message]
2013-09-20 16:24           ` Felipe Balbi
2013-08-15 10:18   ` [PATCH v2 4/9] ARM: OMAP2+: usb-host: Adapt to USB phy-nop RESET line changes Roger Quadros
2013-08-15 10:18     ` Roger Quadros
2013-08-15 10:18   ` [PATCH v2 6/9] ARM: dts: omap4-panda: Use reset-gpios for hsusb1_reset Roger Quadros
2013-08-15 10:18     ` Roger Quadros
2013-08-15 10:18   ` [PATCH v2 9/9] ARM: dts: omap3-beagle-xm: Add USB Host support Roger Quadros
2013-08-15 10:18     ` Roger Quadros
2013-08-15 10:18 ` [PATCH v2 2/9] usb: phy: nop: Don't use regulator framework for RESET line Roger Quadros
2013-08-15 10:18   ` Roger Quadros
2013-09-23 18:05   ` Roger Quadros
2013-09-23 18:05     ` Roger Quadros
2013-08-15 10:18 ` [PATCH v2 5/9] ARM: dts: omap3-beagle: Use reset-gpios for hsusb2_reset Roger Quadros
2013-08-15 10:18   ` Roger Quadros
2013-08-15 10:18 ` [PATCH v2 7/9] ARM: dts: omap5-uevm: " Roger Quadros
2013-08-15 10:18   ` Roger Quadros
2013-08-15 10:18 ` [PATCH v2 8/9] ARM: dts: omap3-beagle: Make USB host pin naming consistent Roger Quadros
2013-08-15 10:18   ` Roger Quadros
2013-08-16 10:52 ` [PATCH v2 0/9] USB: phy: phy-nop: Manage RESET GPIO in the driver Benoit Cousson
2013-08-16 10:52   ` Benoit Cousson
2013-08-19  7:37   ` Roger Quadros
2013-08-19  7:37     ` Roger Quadros

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=20130920162419.GD18721@radagast \
    --to=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=rogerq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.