From: Felipe Balbi <balbi@ti.com>
To: Hema HK <hemahk@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 5/6 v8] OMAP2+: musb: hwmod adaptation for musb registration
Date: Thu, 17 Feb 2011 13:33:21 +0200 [thread overview]
Message-ID: <20110217113321.GA22356@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1297924642-3791-6-git-send-email-hemahk@ti.com>
On Thu, Feb 17, 2011 at 12:07:21PM +0530, Hema HK wrote:
> Using omap_device_build API instead of platform_device_register for
> OMAP2430,OMAP3xxx, OMAP4430 and AM35x musb device registration.
> The device specific resources defined in centralized
> database will be used.
>
> Signed-off-by: Hema HK <hemahk@ti.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Kevin Hilman <khilman@deeprootsystems.com>
> Cc: Cousson, Benoit <b-cousson@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
doesn't apply:
OMAP2+: musb: hwmod adaptation for musb registration
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP3xxx, OMAP4430 and AM35x musb device registration.
The device specific resources defined in centralized
database will be used.
Signed-off-by: Hema HK <hemahk@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Cousson, Benoit <b-cousson@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
--------------------------
Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all y
Applying: OMAP2+: musb: hwmod adaptation for musb registration
error: patch failed: arch/arm/mach-omap2/usb-musb.c:30
error: arch/arm/mach-omap2/usb-musb.c: patch does not apply
Patch failed at 0005 OMAP2+: musb: hwmod adaptation for musb registration
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
--
balbi
next prev parent reply other threads:[~2011-02-17 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 6:37 [PATCH 0/6 v8]usb: musb: hwmod and runtime pm support for musb Hema HK
2011-02-17 6:37 ` [PATCH 1/6 v8] OMAP2430: hwmod data: Add USBOTG Hema HK
2011-02-17 6:37 ` [PATCH 2/6 v8] OMAP3xxx: " Hema HK
[not found] ` <1297924642-3791-1-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2011-02-17 6:37 ` [PATCH 3/6 v8] AM35xx: " Hema HK
2011-02-17 6:37 ` [PATCH 5/6 v8] OMAP2+: musb: hwmod adaptation for musb registration Hema HK
2011-02-17 11:33 ` Felipe Balbi [this message]
[not found] ` <20110217113321.GA22356-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-02-17 11:53 ` Felipe Balbi
2011-02-17 12:11 ` Hema Kalliguddi
2011-02-17 6:37 ` [PATCH 6/6 v8] usb: musb: Using runtime pm APIs for musb Hema HK
2011-02-17 6:37 ` [PATCH 4/6 v8] OMAP4430: hwmod data: Adding USBOTG Hema HK
2011-02-17 11:58 ` [PATCH 0/6 v8]usb: musb: hwmod and runtime pm support for musb Felipe Balbi
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=20110217113321.GA22356@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=b-cousson@ti.com \
--cc=hemahk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@pwsan.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