From: Greg KH <greg@kroah.com>
To: Jonathan Cameron <jic23@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: linux-next: build warning after merge of the staging tree
Date: Fri, 20 Jan 2017 09:37:20 +0100 [thread overview]
Message-ID: <20170120083720.GA29509@kroah.com> (raw)
In-Reply-To: <20170120153622.03c28b85@canb.auug.org.au>
On Fri, Jan 20, 2017 at 03:36:22PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
>
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_I2C_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_I2C && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_I2C)
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_SPI_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_SPI && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_SPI)
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_SPI_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_SPI && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_SPI)
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_I2C_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_I2C && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_I2C)
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_SPI_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_SPI && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_SPI)
> warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_I2C_3AXIS which has unmet direct dependencies (IIO && !SENSORS_LIS3_I2C && IIO_ST_ACCEL_3AXIS && IIO_ST_SENSORS_I2C)
>
> Introduced by commit
>
> 762227721fe6 ("iio: accel: st_accel: handle deprecated bindings")
Ick. I've added Jonathan to the thread, any thoughts?
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-20 8:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 4:36 linux-next: build warning after merge of the staging tree Stephen Rothwell
2017-01-20 8:37 ` Greg KH [this message]
2017-01-20 9:18 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 2:45 Stephen Rothwell
2018-01-16 5:59 ` Greg KH
2018-01-16 10:47 ` Arnd Bergmann
2018-01-16 15:02 ` Greg KH
2018-05-14 4:37 Stephen Rothwell
2018-09-03 2:06 Stephen Rothwell
2018-09-04 9:04 ` John Whitmore
2018-11-08 2:33 Stephen Rothwell
2018-11-08 11:17 ` Greg KH
2019-04-23 5:13 Stephen Rothwell
2019-08-14 6:08 Stephen Rothwell
2019-08-14 7:42 ` Greg KH
2019-08-26 6:24 Stephen Rothwell
2019-08-26 6:30 ` Greg KH
2019-08-26 8:38 ` Gao Xiang
2019-08-26 8:54 ` Gao Xiang
2019-08-26 9:43 ` Gao Xiang
2019-08-26 9:53 ` Gao Xiang
2019-08-26 11:13 ` Gao Xiang
2019-12-13 1:10 Stephen Rothwell
2020-09-09 7:16 Stephen Rothwell
2020-09-09 7:41 ` 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=20170120083720.GA29509@kroah.com \
--to=greg@kroah.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.