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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
