From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
netdev <netdev@vger.kernel.org>,
linux-pci@vger.kernel.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
davem@davemloft.net, Jesse Barnes <jbarnes@virtuousgeek.org>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: [PATCH -next] PCI: fix tlan build when CONFIG_PCI is not enabled
Date: Mon, 14 Feb 2011 12:27:50 -0800 [thread overview]
Message-ID: <20110214122750.e1e03bc8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110214181137.ee8d4c08.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
When CONFIG_PCI is not enabled, tlan.c has a build error:
drivers/net/tlan.c:503: error: implicit declaration of function 'pci_wake_from_d3'
so add an inline function stub for this function to pci.h when
PCI is not enabled, similar to other stubbed PCI functions.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>
---
include/linux/pci.h | 5 +++++
1 file changed, 5 insertions(+)
--- linux-next-20110214.orig/include/linux/pci.h
+++ linux-next-20110214/include/linux/pci.h
@@ -1191,6 +1191,11 @@ static inline int pci_set_power_state(st
return 0;
}
+static inline int pci_wake_from_d3(struct pci_dev *dev, bool enable)
+{
+ return 0;
+}
+
static inline pci_power_t pci_choose_state(struct pci_dev *dev,
pm_message_t state)
{
next prev parent reply other threads:[~2011-02-14 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 7:11 linux-next: Tree for February 14 Stephen Rothwell
2011-02-14 20:27 ` Randy Dunlap [this message]
2011-02-14 20:39 ` [PATCH -next] PCI: fix tlan build when CONFIG_PCI is not enabled David Miller
2011-02-14 21:32 ` Sakari Ailus
2011-02-14 22:02 ` Sakari Ailus
2011-02-16 19:46 ` 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=20110214122750.e1e03bc8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--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.