linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, David Airlie <airlied@linux.ie>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: linux-next: Tree for May 20 (radeon_pm build problem)
Date: Thu, 20 May 2010 12:09:29 -0700	[thread overview]
Message-ID: <20100520120929.364e1f87.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100520163042.9486e077.sfr@canb.auug.org.au>

On Thu, 20 May 2010 16:30:42 +1000 Stephen Rothwell wrote:

> Hi all,
> 
> We are in the merge window again.  I remind you all not to add stuff for
> 2.6.36 to your linux-next trees until after 2.6.35-rc1.
> 
> Changes since 20100519:


CONFIG_DRM_RADEON=y
CONFIG_DRM_RADEON_KMS=y
CONFIG_POWER_SUPPLY=m

causes

radeon_pm.c:(.text+0x13d58f): undefined reference to `power_supply_is_system_supplied'
radeon_pm.c:(.text+0x13e72e): undefined reference to `power_supply_is_system_supplied'


The Kconfig for DRM_RADEON_KMS says:

config DRM_RADEON_KMS
	bool "Enable modesetting on radeon by default - NEW DRIVER"
	depends on DRM_RADEON
	depends on POWER_SUPPLY

Aha.  DRM_RADEON_KMS is a bool, so
	depends on DRM_RADEON && POWER_SUPPLY
evaluates to y.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-05-20 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  6:30 linux-next: Tree for May 20 Stephen Rothwell
2010-05-20 19:09 ` Randy Dunlap [this message]
2010-05-20 19:52 ` linux-next: Tree for May 20 (ceph) Randy Dunlap

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=20100520120929.364e1f87.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).