All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the cpufreq tree
Date: Tue, 26 Apr 2011 22:41:46 -0400	[thread overview]
Message-ID: <20110427024145.GB30804@redhat.com> (raw)
In-Reply-To: <20110427115427.f5a4fac7.sfr@canb.auug.org.au>

On Wed, Apr 27, 2011 at 11:54:27AM +1000, Stephen Rothwell wrote:
 > Removing the source line in kernel/power/Kconfig makes the warnings go
 > away and the only change in the generated config file is this:
 > 
 > @@ -465,10 +465,6 @@
 >  # CONFIG_PM_RUNTIME is not set
 >  CONFIG_PM=y
 >  # CONFIG_PM_DEBUG is not set
 > -
 > -#
 > -# CPU Frequency scaling
 > -#
 >  CONFIG_SECCOMP=y
 >  CONFIG_ISA_DMA_API=y

Ok, thanks for testing. I'll fix something up.

	Dave

  reply	other threads:[~2011-04-27  2:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  1:10 linux-next: build warning after merge of the cpufreq tree Stephen Rothwell
2011-04-27  1:32 ` Dave Jones
2011-04-27  1:54   ` Stephen Rothwell
2011-04-27  2:41     ` Dave Jones [this message]
2011-04-29 20:12     ` Dave Jones
2011-05-02  5:06       ` Stephen Rothwell

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=20110427024145.GB30804@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.