From: Randy Dunlap <rdunlap@xenotime.net>
To: Daniel Drake <dsd@laptop.org>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
Andres Salomon <dilinger@queued.net>,
tglx@linutronix.de, x86@kernel.org
Subject: Re: OLPC power management patches - merge for 3.1?
Date: Sat, 23 Jul 2011 20:20:32 -0700 [thread overview]
Message-ID: <20110723202032.67ebdbcc.rdunlap@xenotime.net> (raw)
In-Reply-To: <CAGq3pz4VHgagUQ+jGJdt9LL4UnFt+CDgcLLXbuVeKfWMc=0wAA@mail.gmail.com>
On Sat, 23 Jul 2011 23:44:09 +0100 Daniel Drake wrote:
> Hi,
>
> Many thanks for committing the OLPC power management patches to
> linux-tip a few weeks ago.
>
> Even though they were never merged into the master branch of linux-tip
> (where I presume linux-next pulls from), they have been included in
> linux-next for even longer via Andrew Morton's tree.
>
> Is there any chance you could send them for inclusion in Linux 3.1?
> The functionality is working well, but a small fixup is needed for
> XO-1.5 (see "[PATCH] x86, olpc-xo15-sci: enable EC wakeup capability"
> from 2011-07-09).
Hi,
I should have posted this sooner...
I have no objection to merging OLPC patches, but they should build
without errors.
>From linux-next 20110722:
arch/x86/built-in.o: In function `battery_status_changed':
olpc-xo15-sci.c:(.text+0x3acdd): undefined reference to `power_supply_get_by_name'
olpc-xo15-sci.c:(.text+0x3ad04): undefined reference to `power_supply_changed'
arch/x86/built-in.o: In function `ac_status_changed':
olpc-xo15-sci.c:(.text+0x3ad4d): undefined reference to `power_supply_get_by_name'
olpc-xo15-sci.c:(.text+0x3ad74): undefined reference to `power_supply_changed'
Looks like this problem is caused by:
config OLPC_XO1_SCI
bool "OLPC XO-1 SCI extras"
depends on OLPC && OLPC_XO1_PM && POWER_SUPPLY
or
config OLPC_XO15_SCI
bool "OLPC XO-1.5 SCI extras"
depends on OLPC && ACPI && POWER_SUPPLY
In both cases, the 'bool' depends on one or more tristate symbols, so
the tristates are satisfied if they are =m or =y. This should work fine
if these kconfig symbols (listed above) were tristate instead of bool.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-24 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 22:44 Daniel Drake
2011-07-24 3:20 ` Randy Dunlap [this message]
2011-07-24 8:59 ` Daniel Drake
2011-07-24 17:13 ` Randy Dunlap
2011-07-24 17:16 ` Daniel Drake
2011-07-24 17:33 ` Randy Dunlap
2011-07-24 17:23 ` Andres Salomon
2011-07-24 7:27 ` Ingo Molnar
2011-07-24 8:55 ` Daniel Drake
2011-07-24 10:18 ` Ingo Molnar
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=20110723202032.67ebdbcc.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®