Linux Input/HID development
 help / color / mirror / Atom feed
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org, "Zhang Lixu" <lixu.zhang@intel.com>
Subject: Re: [PATCH 00/11] HID: iio: warning clean up and prefer kernel coding style
Date: Thu, 18 Jun 2026 00:33:09 +0530	[thread overview]
Message-ID: <AB598E72-247E-46F8-910C-DB7E8AF42FB1@gmail.com> (raw)
In-Reply-To: <CAKqfh0GEeyQ3UMuMupevgPfCon+zccAv302sV5YKCETWMua-xA@mail.gmail.com>



On 17 June 2026 1:00:37 pm IST, Maxwell Doose <m32285159@gmail.com> wrote:
>On Tue, Jun 16, 2026 at 5:26 AM Sanjay Chitroda
><sanjayembeddedse@gmail.com> wrote:
>>
>> Hi all,
>>
>> This series updates HID IIO drivers to resolve checkpatch and
>> kernel coding style issue.
>>
>> This improves readability and follow standard kernel coding style
>> No functional changes are introduced.
>>
>> Testing:
>>   - Compiled with W=1 for each patch in the series
>>
>> ---
>> Sanjay Chitroda (11):
>>       iio: hid-sensors: add missing blank line after declarations
>>       iio: humidity: hid-sensor-humidity: align parenthesis for readability
>>       iio: gyro: hid-sensor-gyro-3d: align parenthesis for readability
>>       iio: magnetometer: hid-sensor-magn-3d: align parenthesis for readability
>>       iio: humidity: hid-sensor-humidity: use common device for devres
>>       iio: position: hid-sensor-custom-intel-hinge: use common device for devres
>>       iio: temperature: hid-sensor-temperature: use common device for devres
>>       iio: hid-sensor-magn-3d: use ! instead of explicit NULL check
>>       iio: hid-sensor-rotation: use ! instead of explicit NULL check
>>       iio: hid-sensor-incl-3d: use ! instead of explicit NULL check
>>       iio: hid-sensor-accel-3d: use ! instead of explicit NULL check
>>
>>  drivers/iio/accel/hid-sensor-accel-3d.c            |  2 +-
>>  .../iio/common/hid-sensors/hid-sensor-trigger.c    |  3 +
>>  drivers/iio/gyro/hid-sensor-gyro-3d.c              | 58 ++++++++--------
>>  drivers/iio/humidity/hid-sensor-humidity.c         | 48 ++++++-------
>>  drivers/iio/magnetometer/hid-sensor-magn-3d.c      | 80 +++++++++++-----------
>>  drivers/iio/orientation/hid-sensor-incl-3d.c       |  2 +-
>>  drivers/iio/orientation/hid-sensor-rotation.c      |  2 +-
>>  .../iio/position/hid-sensor-custom-intel-hinge.c   |  2 +-
>>  drivers/iio/temperature/hid-sensor-temperature.c   |  4 +-
>>  9 files changed, 102 insertions(+), 99 deletions(-)
>
>Firstly, for all of the style patches  (1-4, 8-11):
>
>Reviewed-by: Maxwell Doose <m32285159@gmail.com>
>
Hi Maxwell,
Thank you for the review.

>with Andy's comments.
>
>Secondly, the style fixes are all churn. It would honestly be much
>much better if you were to squash those (even despite the
>one-logical-change-per-patch rule).
I agree with squashing 1-4, common HID drivers-specific changes which cover all HID IIO drivers.

However, this series updates 4 HID drivers, while several other HID IIO drivers needs coding style cleanup.
I'd like to ask Jonathan for his opinion on whether all alignment coding style should be handled in single change, individual change or some logic specific HIO IIO drivers split.

Additionally, 5-7 haven't received any comment/tag. I can consider all changes in v2 and also rebase on latest iio/testing tree to incorporate u32 usage_id change.

Thanks, Sanjay
>

      reply	other threads:[~2026-06-17 19:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 10:26 [PATCH 00/11] HID: iio: warning clean up and prefer kernel coding style Sanjay Chitroda
2026-06-16 10:26 ` [PATCH 01/11] iio: hid-sensors: add missing blank line after declarations Sanjay Chitroda
2026-06-16 11:22   ` sashiko-bot
2026-06-16 10:26 ` [PATCH 02/11] iio: humidity: hid-sensor-humidity: align parenthesis for readability Sanjay Chitroda
2026-06-16 10:57   ` Andy Shevchenko
2026-06-16 11:22   ` sashiko-bot
2026-06-16 10:26 ` [PATCH 03/11] iio: gyro: hid-sensor-gyro-3d: " Sanjay Chitroda
2026-06-16 10:56   ` Andy Shevchenko
2026-06-16 10:26 ` [PATCH 04/11] iio: magnetometer: hid-sensor-magn-3d: " Sanjay Chitroda
2026-06-16 11:19   ` sashiko-bot
2026-06-16 10:26 ` [PATCH 05/11] iio: humidity: hid-sensor-humidity: use common device for devres Sanjay Chitroda
2026-06-16 11:27   ` sashiko-bot
2026-06-16 10:26 ` [PATCH 06/11] iio: position: hid-sensor-custom-intel-hinge: " Sanjay Chitroda
2026-06-16 10:26 ` [PATCH 07/11] iio: temperature: hid-sensor-temperature: " Sanjay Chitroda
2026-06-16 11:27   ` sashiko-bot
2026-06-16 10:26 ` [PATCH 08/11] iio: hid-sensor-magn-3d: use ! instead of explicit NULL check Sanjay Chitroda
2026-06-16 11:01   ` Joshua Crofts
2026-06-16 10:26 ` [PATCH 09/11] iio: hid-sensor-rotation: " Sanjay Chitroda
2026-06-16 10:26 ` [PATCH 10/11] iio: hid-sensor-incl-3d: " Sanjay Chitroda
2026-06-16 11:11 ` [PATCH 11/11] iio: hid-sensor-accel-3d: " Sanjay Chitroda
2026-06-17  7:30 ` [PATCH 00/11] HID: iio: warning clean up and prefer kernel coding style Maxwell Doose
2026-06-17 19:03   ` Sanjay Chitroda [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=AB598E72-247E-46F8-910C-DB7E8AF42FB1@gmail.com \
    --to=sanjayembeddedse@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu.zhang@intel.com \
    --cc=m32285159@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=srinivas.pandruvada@linux.intel.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