From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Keshava Munegowda <keshava_mgowda@ti.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH] mfd: Fix omap_usbhs_alloc_children error handling
Date: Sun, 22 May 2011 21:09:40 +0200 [thread overview]
Message-ID: <20110522190939.GB18610@sortiz-mobl> (raw)
In-Reply-To: <1305353736.11286.2.camel@phoenix>
Hi Axel,
On Sat, May 14, 2011 at 02:15:36PM +0800, Axel Lin wrote:
> 1. Return proper error if omap_usbhs_alloc_child fails
> 2. In the case of goto err_ehci, we should call platform_device_unregister(ehci)
> instead of platform_device_put(ehci) because we have already added the
> platform device to device hierarchy.
Patch applied, thanks a lot.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-05-22 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 6:15 [PATCH] mfd: Fix omap_usbhs_alloc_children error handling Axel Lin
2011-05-16 11:03 ` Munegowda, Keshava
2011-05-16 11:12 ` Felipe Balbi
2011-05-22 19:09 ` Samuel Ortiz [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=20110522190939.GB18610@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=axel.lin@gmail.com \
--cc=balbi@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-kernel@vger.kernel.org \
/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