From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: omap2+: stub out omap*_volt_data
Date: Tue, 11 Oct 2011 15:57:41 +0200 [thread overview]
Message-ID: <201110111557.41396.arnd@arndb.de> (raw)
In-Reply-To: <87ipnwhepq.fsf@ti.com>
On Monday 10 October 2011, Kevin Hilman wrote:
> > I got this build error only now after pulling in the latest omap series, but
> > I cannot tell what caused it. It's also not clear to me if this is the correct
> > solution. Please ack or provide a better fix.
>
> This code was merged for v2.6.39, so not sure why this error is only
> showing up for you now. I just tried a !CONFIG_PM_OPP build on v2.6.39
> and get the same errors, so it's been lingering.
>
> Maybe you haven't had a randconfig that disabled CONFIG_PM_OPP before?
I don't know. The best explanation is that this is a very unlikely case.
I've done many thousand randconfig builds now and have not seen it before.
Of course, since the output of randconfig is random, it could indeed just
be a coincidence.
> Anyways, the fix is fine with me.
Thanks,
Arnd
prev parent reply other threads:[~2011-10-11 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 15:23 [PATCH] ARM: omap2+: stub out omap*_volt_data Arnd Bergmann
2011-10-10 18:41 ` Kevin Hilman
2011-10-11 13:57 ` Arnd Bergmann [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=201110111557.41396.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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