public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Crofts <joshua.crofts1@gmail.com>
To: jic23@kernel.org
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/6] iio: magnetometer: ak8975: modernize and cleanup driver
Date: Wed, 22 Apr 2026 11:22:01 +0000	[thread overview]
Message-ID: <20260422112207.1313-1-joshua.crofts1@gmail.com> (raw)

This series modernizes and cleans up the ak8975 driver, migrating to
more modern kernel APIs and cleaning up legacy code.

Changes include:
 - replacing usleep_range() with fsleep() for optimization
 - migrating to iopoll macros for better device polling
 - removing unused headers and adding new ones
 - checkpatch.pl fixes

v2:
 - PATCH 1: reverted alphabetical header ordering per logical change
   separation
 - PATCH 2: added newline between fsleep() and return
 - PATCH 3: fixed open parenthesis formatting
 - PATCH 4: fixed whitespace issues, added <linux/time.h> for
   USEC_PER_MSEC macro
v3:
 - PATCH 1 & 2: split alphabetical ordering and header removal into two
   separate patches
 - PATCH 4: commit message fix
 - PATCH 5 & 6: split error handling and polling loop replacement into
   two separate patches

Joshua Crofts (6):
  iio: magnetometer: ak8975: sort headers alphabetically
  iio: magnetometer: ak8975: remove unused headers
  iio: magnetometer: ak8975: replace usleep_range() with fsleep()
  iio: magnetometer: ak8975: change 'u8*' to 'u8 *' in cast
  iio: magnetometer: ak8975: fix wrong errno on return
  iio: magnetometer: ak8975: modernize polling loops with iopoll()
    macros

 drivers/iio/magnetometer/ak8975.c | 92 +++++++++++++++----------------
 1 file changed, 45 insertions(+), 47 deletions(-)


base-commit: c65f27cae0deda3316ed49899df4492a3896e38c
-- 
2.47.3


             reply	other threads:[~2026-04-22 11:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 11:22 Joshua Crofts [this message]
2026-04-22 11:22 ` [PATCH v3 1/6] iio: magnetometer: ak8975: sort headers alphabetically Joshua Crofts
2026-04-22 11:22 ` [PATCH v3 2/6] iio: magnetometer: ak8975: remove unused headers Joshua Crofts
2026-04-24 17:58   ` Jonathan Cameron
2026-04-24 18:12     ` Joshua Crofts
2026-04-22 11:22 ` [PATCH v3 3/6] iio: magnetometer: ak8975: replace usleep_range() with fsleep() Joshua Crofts
2026-04-22 11:22 ` [PATCH v3 4/6] iio: magnetometer: ak8975: change 'u8*' to 'u8 *' in cast Joshua Crofts
2026-04-22 11:22 ` [PATCH v3 5/6] iio: magnetometer: ak8975: fix wrong errno on return Joshua Crofts
2026-04-22 13:13   ` Andy Shevchenko
2026-04-22 13:27     ` Joshua Crofts
2026-04-22 11:22 ` [PATCH v3 6/6] iio: magnetometer: ak8975: modernize polling loops with iopoll() macros Joshua Crofts
2026-04-22 13:16 ` [PATCH v3 0/6] iio: magnetometer: ak8975: modernize and cleanup driver Andy Shevchenko
2026-04-22 13:20   ` Joshua Crofts
2026-04-24  8:23   ` Joshua Crofts
2026-04-24 10:18     ` Andy Shevchenko
2026-04-24 10:23       ` Joshua Crofts
2026-04-24 18:02         ` Jonathan Cameron
2026-04-24 18:15           ` Joshua Crofts
2026-04-27 20:15         ` Andy Shevchenko

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=20260422112207.1313-1-joshua.crofts1@gmail.com \
    --to=joshua.crofts1@gmail.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 \
    /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