[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYcR7SA1bfzAtMBpXZiXZeZnV8hWGddx26VvvKwiZC4Sw@mail.gmail.com>
Date: Sun, 2 Jan 2022 08:02:21 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Nikita Yushchenko <nikita.yoush@...entembedded.com>,
Arnd Bergmann <arnd@...db.de>
Cc: Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Alexandru Ardelean <aardelean@...iqon.com>,
Cai Huoqing <caihuoqing@...du.com>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: stm: don't always auto-enable I2C and SPI interface drivers
On Wed, Dec 29, 2021 at 8:29 AM Nikita Yushchenko
<nikita.yoush@...entembedded.com> wrote:
> config IIO_ST_ACCEL_I2C_3AXIS
> - tristate
> - depends on IIO_ST_ACCEL_3AXIS
> - depends on IIO_ST_SENSORS_I2C
> + tristate "STMicroelectronics accelerometers 3-Axis I2C Interface"
> + depends on (I2C && IIO_ST_ACCEL_3AXIS)
> + default y if (I2C && IIO_ST_ACCEL_3AXIS)
> + select IIO_ST_SENSORS_I2C
This thing that a Kconfig symbol is made to depend on itself just
boggles my head but it wouldn't surprise me if KConfig is this weird :(
I CCed Arnd who knows KConfig a bit better than anyone I know.
Yours,
Linus Walleij
Powered by blists - more mailing lists