From: Felipe Balbi <me@felipebalbi.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] musb_hdrc: Clean-up init code for mainline merge
Date: Thu, 12 Feb 2009 21:35:17 +0200 [thread overview]
Message-ID: <20090212193515.GO10711@frodo> (raw)
In-Reply-To: <20090212192059.GB7562@atomide.com>
On Thu, Feb 12, 2009 at 11:21:01AM -0800, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [090212 11:16]:
> > Hi Felipe & Dave,
> >
> > While creating a patch for usb-musb.c init code for mainline
> > kernel, I ended up cleaning up following stuff in the l-o tree.
> >
> > Does it look OK to you?
>
> And here's what the musb_init patch for the mainline. No boards are
> calling musb_init() yet, but that's easy to append.
The attached patch looks nice as well.
> The clock function might cause some merge issues.. I guess eventually
> the driver should just call clk_enable/disable once the omap2 clock
> merge is done.
Yeah, hopefully Russell's work will let us get rid of this
musb_set_clock and use only standard clk_enable/disable() calls.
We only keep that due to different clock names anyway.
--
balbi
next prev parent reply other threads:[~2009-02-12 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 19:16 [PATCH 0/3] musb_hdrc: Clean-up init code for mainline merge Tony Lindgren
2009-02-12 19:16 ` [PATCH 1/3] musb_hdrc: Set musb_resources dynamically Tony Lindgren
2009-02-12 19:28 ` Felipe Balbi
2009-02-12 19:17 ` [PATCH 2/3] musb_hdrc: Clean-up MUSB init code for next merge window Tony Lindgren
2009-02-12 19:30 ` Felipe Balbi
2009-02-12 19:44 ` Tony Lindgren
2009-02-12 19:17 ` [PATCH 3/3] musb_hdrc: Build usb-musb based on config entry, clean-up Makefile Tony Lindgren
2009-02-12 19:31 ` Felipe Balbi
2009-02-12 19:21 ` [PATCH 0/3] musb_hdrc: Clean-up init code for mainline merge Tony Lindgren
2009-02-12 19:35 ` Felipe Balbi [this message]
2009-02-13 20:50 ` David Brownell
2009-02-12 20:49 ` David Brownell
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=20090212193515.GO10711@frodo \
--to=me@felipebalbi.com \
--cc=linux-omap@vger.kernel.org \
--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