public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandru Ardelean <aardelean@deviqon.com>,
	Cai Huoqing <caihuoqing@baidu.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: stm: don't always auto-enable I2C and SPI interface drivers
Date: Mon, 10 Jan 2022 14:25:22 +0200	[thread overview]
Message-ID: <Ydwlsr8WjdsSWvoZ@smile.fi.intel.com> (raw)
In-Reply-To: <20220109124326.3696775-1-nikita.yoush@cogentembedded.com>

On Sun, Jan 09, 2022 at 03:43:26PM +0300, Nikita Yushchenko wrote:
> This patch makes I2C and SPI interface drivers for STMicroelectronics
> sensor chips individually selectable via Kconfig.
> 
> The default is kept unchanged - I2C and SPI interface drivers are still
> selected by default if the corresponding bus support is available.
> 
> However, the patch makes it is possible to explicitly disable drivers
> that are not needed for particular target.

Just noticed, what stm supposed to mean? `git log` against those drivers
suggests something else.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2022-01-10 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 12:43 [PATCH v2] iio: stm: don't always auto-enable I2C and SPI interface drivers Nikita Yushchenko
2022-01-10 11:05 ` Andy Shevchenko
2022-01-10 12:25 ` Andy Shevchenko [this message]
2022-01-10 12:30   ` Nikita Yushchenko
2022-01-10 15:36     ` Andy Shevchenko
2022-01-10 15:50       ` Andy Shevchenko

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=Ydwlsr8WjdsSWvoZ@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=aardelean@deviqon.com \
    --cc=caihuoqing@baidu.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita.yoush@cogentembedded.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox