public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Bryan Wu <cooloney@kernel.org>
Cc: felipe.balbi@nokia.com, David Brownell <david-b@pacbell.net>,
	Felipe Balbi <felipebalbi@users.sourceforge.net>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: HAVE_CLK (for <linux/clk.h> support)
Date: Mon, 1 Sep 2008 13:12:52 +0300	[thread overview]
Message-ID: <20080901101252.GD7041@gandalf.research.nokia.com> (raw)
In-Reply-To: <386072610809010305g2e728e1p282f0a2b8e7ba43e@mail.gmail.com>

On Mon, Sep 01, 2008 at 06:05:19PM +0800, ext Bryan Wu wrote:
> On Mon, Sep 1, 2008 at 6:00 PM, Felipe Balbi <felipe.balbi@nokia.com> wrote:
> > On Mon, Sep 01, 2008 at 05:48:14PM +0800, ext Bryan Wu wrote:
> >> Sorry for jumping in so later. I noticed Blackfin does not support
> >> HAVE_CLK currently.
> >> As the HAVE_CLK dependence is included in the kernel mainline, MUSB
> >> parts do not show up in the Kconfig because of lacking of HAVE_CLK.
> >>
> >> To implement clk infrastructure in Blackfin will be later than merging
> >> MUSB Blackfin parts to upstream.
> >>
> >> Any idea?
> >
> > dude, you're really late on this one. Now that musb depends on HAVE_CLK
> > and we have things working for that. What you can do is locally (on your
> > tree) remove the HAVE_CLK dependency so you can keep musb development
> > going. But don't push that patch upstream. Meanwhile, you'll have time
> > to implement clk framework support for blackfin.
> >
> 
> Too bad, I just realize this when I try to port my local blackfin
> patch for upstream merge.
> You're right, currently I remove the dependency locally. So I need to
> add a new task to implement clk framework for Blackfin.
> 
> OK, another question, do you know where is the latest usb development
> git tree, buddy?

I replied on the other mail :-)

It's a quilt tree on kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/

Just take a look at MAINTAINERS file ;-)

-- 
balbi

  reply	other threads:[~2008-09-01 10:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200805231044.59969.david-b@pacbell.net>
     [not found] ` <1211879340-22013-1-git-send-email-felipe.balbi@nokia.com>
2008-05-27 23:14   ` HAVE_CLK (for <linux/clk.h> support) David Brownell
2008-05-28  0:01     ` Felipe Balbi
2008-05-28  1:41       ` David Brownell
2008-09-01  9:48         ` Bryan Wu
2008-09-01 10:00           ` Felipe Balbi
2008-09-01 10:05             ` Bryan Wu
2008-09-01 10:12               ` Felipe Balbi [this message]
2008-05-28  0:05     ` 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=20080901101252.GD7041@gandalf.research.nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=cooloney@kernel.org \
    --cc=david-b@pacbell.net \
    --cc=felipebalbi@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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