From: Andi Kleen <andi@firstfloor.org>
To: Len Brown <lenb@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: intel idle kconfig warning
Date: Fri, 29 Oct 2010 10:12:02 +0200 [thread overview]
Message-ID: <20101029081202.GC11149@basil.fritz.box> (raw)
In-Reply-To: <alpine.LFD.2.00.1010290053530.4117@localhost.localdomain>
On Fri, Oct 29, 2010 at 01:03:11AM -0400, Len Brown wrote:
>
> > include/config/auto.conf:4352:warning: symbol value 'm' invalid for INTEL_IDLE
> >
> > Some problem with the intel idle Kconfig?
>
> I'm unable to reproduce this warning.
>
> Note that CONFIG_INTEL_IDLE has been boolean since 2.6.36.
> It was tristate in 2.6.35. Is there some sort of stale state
> on your build system?
Hmm yes it went away after cleaning the build dir.
I guess that's a Kbuild bug then that it doesn't handle such changes?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-10-29 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 12:20 intel idle kconfig warning Andi Kleen
2010-10-29 5:03 ` Len Brown
2010-10-29 8:12 ` Andi Kleen [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=20101029081202.GC11149@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@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