From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Neel Bullywon <neelb2403@gmail.com>
Cc: "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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] iio: magnetometer: bmc150_magn: cleanup mutex usage and coding style
Date: Sun, 8 Feb 2026 15:19:45 +0200 [thread overview]
Message-ID: <aYiNcWJyCl71FyEa@smile.fi.intel.com> (raw)
In-Reply-To: <20260206171814.91064-1-neelb2403@gmail.com>
On Fri, Feb 06, 2026 at 12:18:14PM -0500, Neel Bullywon wrote:
> Replace manual mutex lock/unlock calls with guard() to simplify error
>
> handling and reduce goto usage. This ensures RAII-style cleanup where
>
> the mutex is always released automatically.
>
> Replace msleep(5) with usleep_range(5000, 6000) to avoid checkpatch
>
> warnings about short msleep delays.
>
> Also fix several indentation and line wrapping style issues to verify
>
> cleanly with checkpatch.
You commit message is interleaved with unneeded blank lines. Something is wrong
on your side.
> Signed-off-by: Neel Bullywon <neelb2403@gmail.com>
> ---
> Changes in v4:
> - Replace scoped_guard() with guard() to avoid lexical scope issues with goto
> and return values which caused logic errors in previous versions.
> - Replace msleep(5) with usleep_range(5000, 6000) to avoid checkpatch
> warning.
No, please, fix checkpatch first, it should suggest fsleep() and that is
what you should use.
> - Fix indentation and line wrapping to cleanliness.
> - Extend guard() usage to all mutex_lock() instances in the driver.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-02-08 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 17:18 Neel Bullywon
2026-02-07 14:23 ` Jonathan Cameron
2026-02-08 13:19 ` Andy Shevchenko [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=aYiNcWJyCl71FyEa@smile.fi.intel.com \
--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=neelb2403@gmail.com \
--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
all inboxes | Powered by JetHome®