Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Ninad Naik <ninadnaik07@gmail.com>
To: linux@roeck-us.net
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org, me@brighamcampbell.com,
	linux-kernel-mentees@lists.linux.dev,
	Ninad Naik <ninadnaik07@gmail.com>
Subject: [PATCH 0/3] hwmon: lm93: clean up coding style issues
Date: Thu,  7 May 2026 15:41:40 +0530	[thread overview]
Message-ID: <20260507101143.559475-1-ninadnaik07@gmail.com> (raw)

This patch series includes code style changes for lm93 driver to fix
several checkpatch.pl warnings. No functional changes are made. I tested
the changes by compiling the file.

Changes include:
- Add blank lines after variable declarations
- Change 'unsigned' to 'unsigned int'
- Remove else blocks after break or return statements

Ninad Naik (3):
  hwmon: lm93: Add missing blank lines after declarations
  hwmon: lm93: Change unsigned to unsigned int for clarity
  hwmon: lm93: Remove else blocks after break or return for consistency

 drivers/hwmon/lm93.c | 87 ++++++++++++++++++++++++++++----------------
 1 file changed, 56 insertions(+), 31 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-05-07 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 10:11 Ninad Naik [this message]
2026-05-07 10:11 ` [PATCH 1/3] hwmon: lm93: Add missing blank lines after declarations Ninad Naik
2026-05-07 10:11 ` [PATCH 2/3] hwmon: lm93: Change unsigned to unsigned int for clarity Ninad Naik
2026-05-07 21:11   ` sashiko-bot
2026-05-07 10:11 ` [PATCH 3/3] hwmon: lm93: Remove else blocks after break or return for consistency Ninad Naik
2026-05-08 16:27 ` [PATCH 0/3] hwmon: lm93: clean up coding style issues Guenter Roeck

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=20260507101143.559475-1-ninadnaik07@gmail.com \
    --to=ninadnaik07@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=me@brighamcampbell.com \
    --cc=skhan@linuxfoundation.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