From: Arnd Bergmann <arnd@arndb.de>
To: Kevin Hilman <khilman@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Paul Walmsley <paul@pwsan.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [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
WARNING: multiple messages have this Message-ID (diff)
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
next prev parent reply other threads:[~2011-10-11 13:57 UTC|newest]
Thread overview: 6+ 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-08 15:23 ` Arnd Bergmann
2011-10-10 18:41 ` Kevin Hilman
2011-10-10 18:41 ` Kevin Hilman
2011-10-11 13:57 ` Arnd Bergmann [this message]
2011-10-11 13:57 ` Arnd Bergmann
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.de \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.