From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@sang-engineering.com>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2)
Date: Wed, 16 Dec 2015 13:05:20 -0800 [thread overview]
Message-ID: <5671D210.5050306@infradead.org> (raw)
In-Reply-To: <20151216164343.0cb641ce@canb.auug.org.au>
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
next prev parent reply other threads:[~2015-12-16 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 5:43 linux-next: Tree for Dec 16 Stephen Rothwell
2015-12-16 19:28 ` linux-next: Tree for Dec 16 (gpu/drm/vc4) Randy Dunlap
2015-12-17 0:42 ` Eric Anholt
2015-12-17 0:42 ` Eric Anholt
2015-12-16 20:23 ` linux-next: Tree for Dec 16 (lib/842/842_decompress) Randy Dunlap
2015-12-18 14:32 ` Dan Streetman
2015-12-18 16:08 ` Randy Dunlap
2015-12-21 17:12 ` Dan Streetman
2015-12-21 17:52 ` [PATCH] crypto: 842 - remove WARN inside printk Dan Streetman
2015-12-23 10:25 ` Herbert Xu
2015-12-16 21:05 ` Randy Dunlap [this message]
2015-12-16 21:18 ` linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2) Wolfram Sang
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=5671D210.5050306@infradead.org \
--to=rdunlap@infradead.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=wsa@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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.