From: Felipe Balbi <balbi@ti.com>
To: Roger Quadros <rogerq@ti.com>
Cc: devicetree@vger.kernel.org, bcousson@baylibre.com,
tony@atomide.com, linux-usb@vger.kernel.org, balbi@ti.com,
broonie@kernel.org, p.zabel@pengutronix.de,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
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 10:44:06 -0500 [thread overview]
Message-ID: <20130920154406.GV26101@radagast> (raw)
In-Reply-To: <1376561909-4406-4-git-send-email-rogerq@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 453 bytes --]
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 ?
--
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
next parent reply other threads:[~2013-09-20 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376561909-4406-1-git-send-email-rogerq@ti.com>
[not found] ` <1376561909-4406-4-git-send-email-rogerq@ti.com>
2013-09-20 15:44 ` Felipe Balbi [this message]
2013-09-20 16:18 ` [PATCH v2 3/9] ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct usbhs_phy_data Tony Lindgren
2013-09-20 16:24 ` Felipe Balbi
[not found] ` <1376561909-4406-3-git-send-email-rogerq@ti.com>
2013-09-23 18:05 ` [PATCH v2 2/9] usb: phy: nop: Don't use regulator framework for RESET line 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=20130920154406.GV26101@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 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).