From: Arnav Kapoor <kapoorarnav43@gmail.com>
To: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Sean Nyekjaer" <sean@geanix.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Arnav Kapoor" <kapoorarnav43@gmail.com>
Subject: [PATCH v2 0/2] iio: imu: inv_icm42600: fix kernel-doc warnings
Date: Tue, 6 Oct 2026 10:24:02 +0530 [thread overview]
Message-ID: <20261006045413.14320-1-kapoorarnav43@gmail.com> (raw)
Fix the kernel-doc warnings in the inv_icm42600 driver. With this series,
scripts/kernel-doc -Wall reports no warnings for
drivers/iio/imu/inv_icm42600/. Comment-only changes.
Changes in v2:
- Add patch 2 for the remaining kernel-doc -Wall warnings in the
driver (Andy)
- Collect Andy's Reviewed-by on patch 1
- Use the Assisted-by format from coding-assistants.rst (Andy)
v1: https://lore.kernel.org/all/20261003055339.143977-1-kapoorarnav43@gmail.com/
Arnav Kapoor (2):
iio: imu: inv_icm42600: drop stale vdd_supply kernel-doc
iio: imu: inv_icm42600: fix kernel-doc Return: sections
drivers/iio/imu/inv_icm42600/inv_icm42600.h | 1 -
drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c | 4 ++--
drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 4 ++--
3 files changed, 4 insertions(+), 5 deletions(-)
--
2.53.0
next reply other threads:[~2026-10-06 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 4:54 Arnav Kapoor [this message]
2026-10-06 4:54 ` [PATCH v2 1/2] iio: imu: inv_icm42600: drop stale vdd_supply kernel-doc Arnav Kapoor
2026-10-06 4:54 ` [PATCH v2 2/2] iio: imu: inv_icm42600: fix kernel-doc Return: sections Arnav Kapoor
2026-10-06 6:46 ` Joshua Crofts
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=20261006045413.14320-1-kapoorarnav43@gmail.com \
--to=kapoorarnav43@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sean@geanix.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
all inboxes | Powered by JetHome®