From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
lenb@kernel.org, x86@kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: linux-next: Tree for May 30 (apm)
Date: Tue, 31 May 2011 02:00:51 +0200 [thread overview]
Message-ID: <201105310200.51930.rjw@sisk.pl> (raw)
In-Reply-To: <20110530091045.40201b95.randy.dunlap@oracle.com>
On Monday, May 30, 2011, Randy Dunlap wrote:
> On Mon, 30 May 2011 13:35:31 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110527:
> >
> > Linus' tree still has its build failure for which I reverted a commit.
>
>
> 2 randconfigs on i386 failed with:
> ERROR: "pm_idle" [arch/x86/kernel/apm.ko] undefined!
> ERROR: "default_idle" [arch/x86/kernel/apm.ko] undefined!
That appears to be a fallout of the changes that went in through
the Len's idle tree.
Thanks,
Rafael
prev parent reply other threads:[~2011-05-31 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 3:35 linux-next: Tree for May 30 Stephen Rothwell
2011-05-30 16:10 ` linux-next: Tree for May 30 (apm) Randy Dunlap
2011-05-31 0:00 ` Rafael J. Wysocki [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=201105310200.51930.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jkosina@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--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