public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: jbarnes@virtuousgeek.org, 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>
Subject: Re: next-0708: build failure at drivers/pci/pci-acpi.c
Date: Tue, 8 Jul 2008 17:12:22 +0200	[thread overview]
Message-ID: <200807081712.23937.rjw@sisk.pl> (raw)
In-Reply-To: <a4423d670807080518g31402f60j2f624a2ac2db03aa@mail.gmail.com>

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.

In that case the appended patch should help.  Please test and report back (I
can't test linux-next compilation at the moment).

Thanks,
Rafael

---
From: Rafael J. Wysocki <rjw@sisk.pl>

PCI ACPI: Fix compilation of pci-acpi.c

Fix compilation of pci-acpi.c with CONFIG_ACPI set and
CONFIG_PM_SLEEP unset.

Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
 include/acpi/acpi_bus.h |    4 ++++
 1 file changed, 4 insertions(+)

Index: linux-next/include/acpi/acpi_bus.h
===================================================================
--- linux-next.orig/include/acpi/acpi_bus.h
+++ linux-next/include/acpi/acpi_bus.h
@@ -388,6 +388,10 @@ static inline int acpi_pm_device_sleep_s
 		*p = ACPI_STATE_D0;
 	return ACPI_STATE_D3;
 }
+static inline int acpi_pm_device_sleep_wake(struct device *d, bool b)
+{
+	return -ENOSYS;
+}
 #endif /* !CONFIG_PM_SLEEP */
 
 #endif				/* CONFIG_ACPI */

  reply	other threads:[~2008-07-08 15:12 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 [this message]
2008-07-08 16:29   ` Alexander Beregalov
2008-07-08 16:58     ` Rafael J. Wysocki
2008-07-08 17:40       ` Jesse Barnes
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=200807081712.23937.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.beregalov@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --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 \
    /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