From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com
Subject: Re: linux-next: Tree for Mar 23 (xen-acpi)
Date: Sat, 24 Mar 2012 09:22:44 -0400 [thread overview]
Message-ID: <20120324132243.GA17787@phenom.dumpdata.com> (raw)
In-Reply-To: <20120324125311.GA15144@phenom.dumpdata.com>
On Sat, Mar 24, 2012 at 08:53:11AM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Mar 23, 2012 at 10:30:18AM -0700, Randy Dunlap wrote:
> > On 03/22/2012 11:23 PM, Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Reminder: please do not add stuff destined for v3.5 to linux-next
> > > included trees/branches until after v3.4-rc1 has been released.
> > >
> > > Changes since 20120322:
> >
> >
> > on x86_64:
> >
> > ERROR: "acpi_processor_unregister_performance" [drivers/xen/xen-acpi-processor.ko] undefined!
> > ERROR: "acpi_processor_notify_smm" [drivers/xen/xen-acpi-processor.ko] undefined!
> > ERROR: "acpi_processor_register_performance" [drivers/xen/xen-acpi-processor.ko] undefined!
> > ERROR: "acpi_processor_preregister_performance" [drivers/xen/xen-acpi-processor.ko] undefined!
> >
> >
> > Full randconfig file is attached.
>
> Thanks. Working on a fix.
Fixed. Patch going to show in #linux-next shortly.
prev parent reply other threads:[~2012-03-24 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 6:23 linux-next: Tree for Mar 23 Stephen Rothwell
2012-03-23 10:29 ` linux-next: Tree for Mar 23: doubled patch in vmscan.c Hugh Dickins
2012-03-23 12:50 ` Stephen Rothwell
2012-03-23 17:30 ` linux-next: Tree for Mar 23 (xen-acpi) Randy Dunlap
2012-03-24 12:53 ` Konrad Rzeszutek Wilk
2012-03-24 13:22 ` Konrad Rzeszutek Wilk [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=20120324132243.GA17787@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=xen-devel@lists.xensource.com \
/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.