From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
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>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: next-0708: build failure at drivers/pci/pci-acpi.c
Date: Thu, 10 Jul 2008 02:16:44 +0200 [thread overview]
Message-ID: <200807100216.45690.rjw@sisk.pl> (raw)
In-Reply-To: <200807091621.37697.jbarnes@virtuousgeek.org>
On Thursday, 10 of July 2008, Jesse Barnes wrote:
> On Tuesday, July 8, 2008 1:29:31 pm Rafael J. Wysocki wrote:
> > On Tuesday, 8 of July 2008, Jesse Barnes wrote:
> > > David sent me one just like this at 7am this morning, just applied and
> > > pushed (along with Alexander's tested-by).
> >
> > OK, thanks.
> >
> > Would you like me to send the Stephen's fix for compilation on ppc64
> > (CONFIG_PM unset)?
>
> Sure, unless it's already in the ppc tree...
It looks like Stephen had to apply it today too, so I guess it isn't.
Thanks,
Rafael
---
From: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] pci: include linux/pm_wakeup.h for device_set_wakeup_capable
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
drivers/pci/pci.c | 1 +
include/linux/pm_wakeup.h | 2 ++
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index e632a58..3d92b71 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -17,6 +17,7 @@
#include <linux/string.h>
#include <linux/log2.h>
#include <linux/pci-aspm.h>
+#include <linux/pm_wakeup.h>
#include <asm/dma.h> /* isa_dma_bridge_buggy */
#include "pci.h"
diff --git a/include/linux/pm_wakeup.h b/include/linux/pm_wakeup.h
index 3af0c8d..0aae777 100644
--- a/include/linux/pm_wakeup.h
+++ b/include/linux/pm_wakeup.h
@@ -63,6 +63,8 @@ static inline void device_init_wakeup(struct device *dev, int val)
dev->power.can_wakeup = !!val;
}
+static inline void device_set_wakeup_capable(struct device *dev, int val) { }
+
static inline int device_can_wakeup(struct device *dev)
{
return dev->power.can_wakeup;
--
next prev parent reply other threads:[~2008-07-10 0:16 UTC|newest]
Thread overview: 18+ 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 12:18 ` Alexander Beregalov
2008-07-08 15:12 ` Rafael J. Wysocki
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 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-09 23:21 ` Jesse Barnes
2008-07-10 0:16 ` Rafael J. Wysocki [this message]
2008-07-14 21:30 ` Jesse Barnes
2008-07-14 21:30 ` Jesse Barnes
2008-07-10 0:16 ` Rafael J. Wysocki
2008-07-08 20:29 ` Rafael J. Wysocki
2008-07-08 17:40 ` Jesse Barnes
2008-07-08 16:29 ` Alexander Beregalov
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=200807100216.45690.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=a.beregalov@gmail.com \
--cc=ak@linux.intel.com \
--cc=dhowells@redhat.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 \
--cc=sfr@canb.auug.org.au \
/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.