From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: st_sensors: correct kernel-doc issues
Date: Thu, 12 Mar 2026 12:33:43 +0200 [thread overview]
Message-ID: <abKWh4ACsYzTI9fr@ashevche-desk.local> (raw)
In-Reply-To: <20260312051347.681042-1-rdunlap@infradead.org>
On Wed, Mar 11, 2026 at 10:13:45PM -0700, Randy Dunlap wrote:
> Use the proper kernel-doc format and struct member names to avoid
> kernel-doc warnings:
>
> Warning: include/linux/iio/common/st_sensors.h:184 struct member 'int1'
> not described in 'st_sensor_data_ready_irq'
> Warning: ../include/linux/iio/common/st_sensors.h:184 struct member 'int2'
> not described in 'st_sensor_data_ready_irq'
> Warning: ../include/linux/iio/common/st_sensors.h:184 struct member
> 'stat_drdy' not described in 'st_sensor_data_ready_irq'
> Warning: ../include/linux/iio/common/st_sensors.h:184 struct member 'ig1'
> not described in 'st_sensor_data_ready_irq'
> Warning: ../include/linux/iio/common/st_sensors.h:219 struct member
> 'num_ch' not described in 'st_sensor_settings'
> Warning: ../include/linux/iio/common/st_sensors.h:263 struct member
> 'num_data_channels' not described in 'st_sensor_data'
Thanks, it's a good patch for this driver!
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-12 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 5:13 Randy Dunlap
2026-03-12 10:33 ` Andy Shevchenko [this message]
2026-03-22 11:53 ` Jonathan Cameron
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=abKWh4ACsYzTI9fr@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rdunlap@infradead.org \
/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®