From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
ak@linux.intel.com, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-next@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
David Howells <dhowells@redhat.com>
Subject: Re: next-0708: build failure at drivers/pci/pci-acpi.c
Date: Tue, 8 Jul 2008 10:40:38 -0700 [thread overview]
Message-ID: <200807081040.38777.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200807081858.16321.rjw@sisk.pl>
On Tuesday, July 08, 2008 9:58 am Rafael J. Wysocki wrote:
> On Tuesday, 8 of July 2008, Alexander Beregalov wrote:
> > 2008/7/8 Rafael J. Wysocki <rjw@sisk.pl>:
> > > On Tuesday, 8 of July 2008, Alexander Beregalov wrote:
> > >> Hi Rafael
> > >>
> > >> drivers/pci/pci-acpi.c: In function 'acpi_pci_sleep_wake':
> > >> drivers/pci/pci-acpi.c:311: error: implicit declaration of function
> > >> 'acpi_pm_device_sleep_wake'
> > >
> > > I guess this is a compilation with CONFIG_ACPI=y and CONFIG_PM_SLEEP
> > > unset.
> >
> > Indeed.
> >
> > > In that case the appended patch should help. Please test and report
> > > back (I can't test linux-next compilation at the moment).
> >
> > Compilation test passed and the kernel can boot.
>
> Thanks!
>
> Jesse, could you please apply the patch below to the linux-next branch, on
> top of the PCI wake-up patchset?
>
> Rafael
David sent me one just like this at 7am this morning, just applied and pushed
(along with Alexander's tested-by).
Thanks,
Jesse
next prev parent reply other threads:[~2008-07-08 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 12:18 next-0708: build failure at drivers/pci/pci-acpi.c Alexander Beregalov
2008-07-08 15:12 ` Rafael J. Wysocki
2008-07-08 16:29 ` Alexander Beregalov
2008-07-08 16:58 ` Rafael J. Wysocki
2008-07-08 17:40 ` Jesse Barnes [this message]
2008-07-08 20:29 ` Rafael J. Wysocki
2008-07-09 23:21 ` Jesse Barnes
2008-07-10 0:16 ` Rafael J. Wysocki
2008-07-14 21:30 ` Jesse Barnes
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=200807081040.38777.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=a.beregalov@gmail.com \
--cc=ak@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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