LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm <akpm@linux-foundation.org>, Ba Zheng <zheng.ba@intel.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jean Delvare <khali@linux-fr.org>,
Ben Dooks <ben-linux@fluff.org>,
linux-i2c@vger.kernel.org
Subject: [PATCH -next] i2c: intel-mid depends on PCI
Date: Fri, 29 Oct 2010 13:37:09 -0700 [thread overview]
Message-ID: <20101029133709.5e5df4ad.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101029121148.d27e03bc.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
i2c-intel-mid driver uses PCI data structs and interfaces,
so it should depend on PCI. Fixes these build errors:
drivers/i2c/busses/i2c-intel-mid.c:977: error: implicit declaration of function 'pci_request_region'
drivers/i2c/busses/i2c-intel-mid.c:1077: error: implicit declaration of function 'pci_release_region'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Ba Zheng <zheng.ba@intel.com>
Cc: Jean Delvare <khali@linux-fr.org>
Cc: Ben Dooks <ben-linux@fluff.org>
Cc: linux-i2c@vger.kernel.org
---
drivers/i2c/busses/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20101029.orig/drivers/i2c/busses/Kconfig
+++ linux-next-20101029/drivers/i2c/busses/Kconfig
@@ -398,6 +398,7 @@ config I2C_IMX
config I2C_INTEL_MID
tristate "Intel Moorestown/Medfield Platform I2C controller"
+ depends on PCI
help
Say Y here if you have an Intel Moorestown/Medfield platform I2C
controller.
next prev parent reply other threads:[~2010-10-29 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 1:11 linux-next: Tree for October 29 Stephen Rothwell
2010-10-29 20:37 ` Randy Dunlap [this message]
2010-10-29 23:16 ` linux-next: Tree for October 29 (staging/ath6kl) Randy Dunlap
2010-10-29 23:51 ` Greg KH
2010-11-02 18:37 ` Vipin Mehta
2010-11-02 20:02 ` Greg KH
2010-11-03 13:31 ` Greg KH
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=20101029133709.5e5df4ad.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zheng.ba@intel.com \
--subject='Re: [PATCH -next] i2c: intel-mid depends on PCI' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).