From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: nuno.sa@analog.com, linux-iio@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Dragos Bogdan <dragos.bogdan@analog.com>
Subject: Re: [PATCH 0/4] iio: imu: drop #ifdef around CONFIG_DEBUG_FS
Date: Sat, 10 Aug 2024 11:41:19 +0100 [thread overview]
Message-ID: <20240810114119.15917ccc@jic23-huawei> (raw)
In-Reply-To: <20240809-dev-adis-debugfs-improv-v1-0-d3adb6996518@analog.com>
On Fri, 09 Aug 2024 11:17:05 +0200
Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:
> Hi,
>
> Small series to make the IMUs debugfs code a bit neater. As mentioned in
> the commit message, let's allow the compiler to drop any unused instead
> of guarding it with #ifdefs.
Applied.
>
> ---
> Nuno Sa (4):
> iio: imu: adis16475: drop ifdef around CONFIG_DEBUG_FS
> iio: imu: adis16480: drop ifdef around CONFIG_DEBUG_FS
> iio: imu: adis16400: drop ifdef around CONFIG_DEBUG_FS
> iio: imu: adis16460: drop ifdef around CONFIG_DEBUG_FS
>
> drivers/iio/imu/adis16400.c | 18 ++++--------------
> drivers/iio/imu/adis16460.c | 18 ++++--------------
> drivers/iio/imu/adis16475.c | 9 +++------
> drivers/iio/imu/adis16480.c | 18 ++++--------------
> 4 files changed, 15 insertions(+), 48 deletions(-)
> ---
> base-commit: 7cad163c39cb642ed587d3eeb37a5637ee02740f
> change-id: 20240809-dev-adis-debugfs-improv-e007579b5262
> --
>
> Thanks!
> - Nuno Sá
>
>
prev parent reply other threads:[~2024-08-10 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 9:17 [PATCH 0/4] iio: imu: drop #ifdef around CONFIG_DEBUG_FS Nuno Sa via B4 Relay
2024-08-09 9:17 ` [PATCH 1/4] iio: imu: adis16475: drop ifdef " Nuno Sa via B4 Relay
2024-08-09 9:17 ` [PATCH 2/4] iio: imu: adis16480: " Nuno Sa via B4 Relay
2024-08-09 9:17 ` [PATCH 3/4] iio: imu: adis16400: " Nuno Sa via B4 Relay
2024-08-09 9:17 ` [PATCH 4/4] iio: imu: adis16460: " Nuno Sa via B4 Relay
2024-08-10 10:41 ` Jonathan Cameron [this message]
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=20240810114119.15917ccc@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devnull+nuno.sa.analog.com@kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.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