On Fri, Jun 09, 2017 at 12:31:10PM +0200, Peter Rosin wrote:
> On 2017-06-09 12:22, Arnd Bergmann wrote:
> > COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot
> > compile
> > in that configuration:
>
> Ouch, thanks for catching!
>
> Reviewed-by: Peter Rosin
On Fri, Jun 09, 2017 at 12:31:10PM +0200, Peter Rosin wrote:
> On 2017-06-09 12:22, Arnd Bergmann wrote:
> > COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot
> > compile
> > in that configuration:
>
> Ouch, thanks for catching!
>
> Reviewed-by: Peter Rosin
>
> Greg, I
On 2017-06-09 12:22, Arnd Bergmann wrote:
> COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
> in that configuration:
Ouch, thanks for catching!
Reviewed-by: Peter Rosin
Greg, I assume you will you be taking this?
Cheers,
peda
On 2017-06-09 12:22, Arnd Bergmann wrote:
> COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
> in that configuration:
Ouch, thanks for catching!
Reviewed-by: Peter Rosin
Greg, I assume you will you be taking this?
Cheers,
peda
COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
in that configuration:
drivers/mux/mux-adg792a.c: In function 'adg792a_write_cmd':
drivers/mux/mux-adg792a.c:34:9: error: implicit declaration of function
'i2c_smbus_write_byte_data'; did you mean
COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
in that configuration:
drivers/mux/mux-adg792a.c: In function 'adg792a_write_cmd':
drivers/mux/mux-adg792a.c:34:9: error: implicit declaration of function
'i2c_smbus_write_byte_data'; did you mean
6 matches
Mail list logo