From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Cc: "Pan Chuang" <panchuang@vivo.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/13] iio: common: Remove redundant dev_err()
Date: Sat, 18 Jul 2026 09:35:02 +0300 [thread overview]
Message-ID: <alselrjckmvvNdk1@ashevche-desk.local> (raw)
In-Reply-To: <20260718002557.2e530d50@jic23-huawei>
On Sat, Jul 18, 2026 at 12:26:09AM +0100, Jonathan Cameron wrote:
> On Fri, 17 Jul 2026 17:42:27 +0800
> Pan Chuang <panchuang@vivo.com> wrote:
>
> Where there is only one driver affected, please name that driver
> in the commit message. Let's anyone who cares about other drivers
> in that directory know they can ignore it!
Yep. the hint is to use
git log --oneline --no-merges -- $FILE(S)
to see the practical appearance, id est here (I cut the summaries):
git log --oneline --no-merges -- drivers/iio/common/st_sensors/st_sensors_trigger.c
9f92e93e257b iio: common: st_sensors:
cdd30ebb1b9f module:
d5ab4e9a10ae iio: common: st:
f700e55ef6ef iio:
0805b5121f29 iio:st-sensors:
d4786e7df03d iio:st-sensors:
e42696515414 iio: st_sensors:
82bcb7fb6498 iio: st_sensors:
9c6cd755b548 iio: st-sensors:
...and so on with the prevailing of "iio: st_sensors:".
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-18 6:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:42 [PATCH 00/13] iio: Remove redundant error messages on IRQ request failure Pan Chuang
2026-07-17 9:42 ` [PATCH 01/13] iio: accel: Remove redundant dev_err()/dev_err_probe() Pan Chuang
2026-07-17 23:21 ` Jonathan Cameron
2026-07-18 6:30 ` Andy Shevchenko
2026-07-17 9:42 ` [PATCH 02/13] iio: addac: Remove redundant dev_err_probe() Pan Chuang
2026-07-17 9:42 ` [PATCH 03/13] iio: chemical: Remove redundant dev_err()/dev_err_probe() Pan Chuang
2026-07-17 22:05 ` Maxwell Doose
2026-07-17 23:24 ` Jonathan Cameron
2026-07-18 9:11 ` Maxwell Doose
2026-07-18 6:28 ` Andy Shevchenko
2026-07-17 9:42 ` [PATCH 04/13] iio: common: Remove redundant dev_err() Pan Chuang
2026-07-17 23:26 ` Jonathan Cameron
2026-07-18 6:35 ` Andy Shevchenko [this message]
2026-07-17 9:42 ` [PATCH 05/13] iio: gyro: Remove redundant dev_err_probe() Pan Chuang
2026-07-17 9:42 ` [PATCH 06/13] iio: health: Remove redundant dev_err() Pan Chuang
2026-07-17 9:42 ` [PATCH 07/13] iio: humidity: Remove redundant dev_err()/dev_err_probe() Pan Chuang
2026-07-17 9:42 ` [PATCH 08/13] iio: imu: " Pan Chuang
2026-07-17 9:42 ` [PATCH 09/13] iio: magnetometer: Remove redundant dev_err() Pan Chuang
2026-07-17 9:42 ` [PATCH 10/13] iio: pressure: Remove redundant dev_err()/dev_err_probe() Pan Chuang
2026-07-17 9:42 ` [PATCH 11/13] iio: proximity: " Pan Chuang
2026-07-17 9:42 ` [PATCH 12/13] iio: light: " Pan Chuang
2026-07-17 9:42 ` [PATCH 13/13] iio: temperature: " Pan Chuang
2026-07-17 10:30 ` [PATCH 00/13] iio: Remove redundant error messages on IRQ request failure 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=alselrjckmvvNdk1@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=panchuang@vivo.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
Powered by JetHome