From: Felipe Balbi <felipe.balbi@nokia.com>
To: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>
Cc: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: clk2xxx.c doesn't compile if CPUFREQ is enabled
Date: Sat, 26 Dec 2009 01:38:11 +0200 [thread overview]
Message-ID: <20091225233811.GA18606@nokia.com> (raw)
In-Reply-To: <1261784154-18550-1-git-send-email-felipe.balbi@nokia.com>
On Sat, Dec 26, 2009 at 12:35:54AM +0100, Balbi Felipe (Nokia-D/Helsinki) wrote:
>Hi Paul,
>
>if we enable CPUFREQ we can't build omap2 for two reasons,
>one of them is fixed by the patch below but the other one
>it seems like it'll need more invasive changes to the code
>so I'll leave it for you to decide how to do it.
>
>It's basically failing because the __musb_be_array() check
oops, it comes out naturally. Should be __must_be_array() hehe.
--
balbi
next prev parent reply other threads:[~2009-12-25 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 23:35 clk2xxx.c doesn't compile if CPUFREQ is enabled Felipe Balbi
2009-12-25 23:38 ` Felipe Balbi [this message]
2009-12-30 9:09 ` Paul Walmsley
2009-12-30 12:30 ` [PATCH] arm: omap2: " 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=20091225233811.GA18606@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=linux-omap@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