* Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) [not found] <20150217160221.1a15340e@canb.auug.org.au> @ 2015-02-17 18:28 ` Randy Dunlap 2015-02-17 19:11 ` Wolfram Sang 0 siblings, 1 reply; 3+ messages in thread From: Randy Dunlap @ 2015-02-17 18:28 UTC (permalink / raw) To: Stephen Rothwell, linux-next; +Cc: linux-kernel, David E. Box, linux-i2c On 02/16/15 21:02, Stephen Rothwell wrote: > Hi all, > > Please do not add any material destined for v3.21 to your linux-next > included trees until after v3.20-rc1 has been released. > > Changes since 20150216: > on i386, when CONFIG_IOSF_MBI=m and CONFIG_I2C_DESIGNWARE_BAYTRAIL=y: drivers/built-in.o: In function `i2c_dw_eval_lock_support': (.text+0x37dd74): undefined reference to `iosf_mbi_available' drivers/built-in.o: In function `reset_semaphore.isra.1': i2c-designware-baytrail.c:(.text+0x37ddd1): undefined reference to `iosf_mbi_read' i2c-designware-baytrail.c:(.text+0x37de13): undefined reference to `iosf_mbi_write' drivers/built-in.o: In function `baytrail_i2c_acquire': (.text+0x37df26): undefined reference to `iosf_mbi_write' drivers/built-in.o: In function `baytrail_i2c_acquire': (.text+0x37dfab): undefined reference to `iosf_mbi_read' drivers/built-in.o: In function `baytrail_i2c_acquire': (.text+0x37e080): undefined reference to `iosf_mbi_read' because IOSF_MBI is tristate and I2C_DESIGNWARE_BAYTRAIL is bool: config I2C_DESIGNWARE_BAYTRAIL bool "Intel Baytrail I2C semaphore support" depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI && ACPI I suppose someone could make that: depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. -- ~Randy ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) 2015-02-17 18:28 ` linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) Randy Dunlap @ 2015-02-17 19:11 ` Wolfram Sang 2015-02-17 20:59 ` David E. Box 0 siblings, 1 reply; 3+ messages in thread From: Wolfram Sang @ 2015-02-17 19:11 UTC (permalink / raw) To: Randy Dunlap Cc: Stephen Rothwell, linux-next, linux-kernel, David E. Box, linux-i2c [-- Attachment #1: Type: text/plain, Size: 376 bytes --] Randy, thanks for the report! > I suppose someone could make that: > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. I'll wait a day for input from David what he prefers, because I don't own/know this platform. If there is no response, I'll apply the first solution. Wolfram [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) 2015-02-17 19:11 ` Wolfram Sang @ 2015-02-17 20:59 ` David E. Box 0 siblings, 0 replies; 3+ messages in thread From: David E. Box @ 2015-02-17 20:59 UTC (permalink / raw) To: Wolfram Sang Cc: Randy Dunlap, Stephen Rothwell, linux-next, linux-kernel, linux-i2c Hi Wolfram, On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote: > Randy, > > thanks for the report! > > > I suppose someone could make that: > > > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. > > I'll wait a day for input from David what he prefers, because I don't > own/know this platform. If there is no response, I'll apply the first > solution. > This is fine with me. I own IOSF_MBI as well. Thanks. Dave ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-02-17 20:59 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20150217160221.1a15340e@canb.auug.org.au> 2015-02-17 18:28 ` linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) Randy Dunlap 2015-02-17 19:11 ` Wolfram Sang 2015-02-17 20:59 ` David E. Box
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).