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 17:36:07 +0200 [thread overview]
Message-ID: <YdxSZ53cBGcNjbvb@smile.fi.intel.com> (raw)
In-Reply-To: <13907dd6-2a30-c6b1-fb71-e88dba98f5ca@cogentembedded.com>
On Mon, Jan 10, 2022 at 03:30:08PM +0300, Nikita Yushchenko wrote:
> > Just noticed, what stm supposed to mean? `git log` against those drivers
> > suggests something else.
>
> I copied it from git log, can't remember from where exactly.
> Perhaps 'st_sensors' is better.
% git log --no-merges --oneline -- drivers/iio/common/st_sensors/ drivers/iio/*/st_* | cut -f2-4 -d' ' | grep -o "[ :]st[^:]\+:" | tr -d ':' | tr -d ' ' | sort | uniq -c | sort -n
1 st_accel_core
1 st_accel_i2c
1 st_gyro_spi
1 st_lsm9ds0
1 st_lsmdsx
1 st-magn
1 st_magn_core
1 st_pressure_core
1 stsensors
2 st_accel_i2c.c
2 st_magn_spi
2 st_press
2 st_pressure_spi
3 st-accel
4 st_accel_spi
4 st_uvis25
5 st-sensors
11 st_gyro
15 st_magn
21 st_pressure
27 st_accel
68 st_sensors
140 st_lsm6dsx
(Yes, I know that command line can be simplified :-)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-10 15:37 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
2022-01-10 12:30 ` Nikita Yushchenko
2022-01-10 15:36 ` Andy Shevchenko [this message]
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=YdxSZ53cBGcNjbvb@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;
as well as URLs for NNTP newsgroup(s).