linux-kernel - Re: linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5671D210.5050306@infradead.org>
Date:	Wed, 16 Dec 2015 13:05:20 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org,
	Wolfram Sang <wsa@...g-engineering.com>,
	linux-i2c@...r.kernel.org, Wolfram Sang <wsa@...-dreams.de>
Subject: Re: linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2)

On 12/15/15 21:43, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20151215:
> 
> The drm-misc tree gained a conflict against Linus' tree.
> 
> The i2c tree gained a build failure for which I applied a patch.
> 
> The gpio tree gained a build failure so I used the version from
> next-20151215.
> 

on x86_64, when CONFIG_I2C_SLAVE is not enabled:



../drivers/i2c/busses/i2c-emev2.c: In function 'em_i2c_slave_irq':
../drivers/i2c/busses/i2c-emev2.c:233:23: error: storage size of 'event' isn't known
  enum i2c_slave_event event;
                       ^
../drivers/i2c/busses/i2c-emev2.c:250:3: error: implicit declaration of function 'i2c_slave_event' [-Werror=implicit-function-declaration]
   i2c_slave_event(priv->slave, I2C_SLAVE_STOP, &value);
   ^
../drivers/i2c/busses/i2c-emev2.c:250:32: error: 'I2C_SLAVE_STOP' undeclared (first use in this function)
   i2c_slave_event(priv->slave, I2C_SLAVE_STOP, &value);
                                ^
../drivers/i2c/busses/i2c-emev2.c:250:32: note: each undeclared identifier is reported only once for each function it appears in
../drivers/i2c/busses/i2c-emev2.c:270:5: error: 'I2C_SLAVE_READ_REQUESTED' undeclared (first use in this function)
     I2C_SLAVE_READ_REQUESTED :
     ^
../drivers/i2c/busses/i2c-emev2.c:271:5: error: 'I2C_SLAVE_READ_PROCESSED' undeclared (first use in this function)
     I2C_SLAVE_READ_PROCESSED;
     ^
../drivers/i2c/busses/i2c-emev2.c:286:33: error: 'I2C_SLAVE_WRITE_REQUESTED' undeclared (first use in this function)
    i2c_slave_event(priv->slave, I2C_SLAVE_WRITE_REQUESTED,
                                 ^
../drivers/i2c/busses/i2c-emev2.c:292:6: error: 'I2C_SLAVE_WRITE_RECEIVED' undeclared (first use in this function)
      I2C_SLAVE_WRITE_RECEIVED, &value);
      ^
../drivers/i2c/busses/i2c-emev2.c:233:23: warning: unused variable 'event' [-Wunused-variable]
  enum i2c_slave_event event;
                       ^
../drivers/i2c/busses/i2c-emev2.c: At top level:
../drivers/i2c/busses/i2c-emev2.c:353:2: error: unknown field 'reg_slave' specified in initializer
  .reg_slave      = em_i2c_reg_slave,
  ^
../drivers/i2c/busses/i2c-emev2.c:353:2: warning: excess elements in struct initializer [enabled by default]
../drivers/i2c/busses/i2c-emev2.c:353:2: warning: (near initialization for 'em_i2c_algo') [enabled by default]
../drivers/i2c/busses/i2c-emev2.c:354:2: error: unknown field 'unreg_slave' specified in initializer
  .unreg_slave    = em_i2c_unreg_slave,
  ^
../drivers/i2c/busses/i2c-emev2.c:354:2: warning: excess elements in struct initializer [enabled by default]
../drivers/i2c/busses/i2c-emev2.c:354:2: warning: (near initialization for 'em_i2c_algo') [enabled by default]
cc1: some warnings being treated as errors
../scripts/Makefile.build:264: recipe for target 'drivers/i2c/busses/i2c-emev2.o' failed

-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/