mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
	andy@kernel.org, sakari.ailus@linux.intel.com,
	christoph.muellner@theobroma-systems.com, martink@posteo.de,
	mfuzzey@parkeon.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/10] iio: accel: mma8452: improve coding style, pm and resource cleanup
Date: Mon, 18 May 2026 10:20:25 +0300	[thread overview]
Message-ID: <agq9uWCrS3txgO5B@ashevche-desk.local> (raw)
In-Reply-To: <agogfypMDl6dS9D6@hu-ckantibh-hyd.qualcomm.com>

On Mon, May 18, 2026 at 01:39:35AM +0530, Sanjay Chitroda wrote:
> On Tue, May 05, 2026 at 11:16:30PM +0530, Sanjay Chitroda wrote:
> > 
> > This series contains a small fixes, cleanup and improvements to use
> > modern kernel helper API and coding style for mma8452 accel driver.
> > 
> > The changes modernize mutex with guard(), dev_err_probe usage,
> > resolve checkpatch CHECKS and pm_ptr macro usage.
> > 
> > Changes in v3:
> > - Following input from Andy and Jonathan added new changes as following
> >   0001: handle return value to have proper error propagation
> >   0002: use non-devm API to maintain resource management LIFO order
> >   0006: convert individual regulator using bulk regulator API
> >   0009: use IIO cleanup helper for DIRECT_MODE
> > - Address kernel coding stype specific review comment
> > - Reorder local struct device and dev_err_probe change
> > v2 series -> https://lore.kernel.org/all/20260422165643.2148195-1-sanjayembedded@gmail.com/
> > Changes in v2:
> > - 0005: address review comment from Andy and Geert
> >   and use DEFINE_RUNTIME_DEV_PM_OPS macro
> > - Added new cleanup channges in mma8452 driver
> > 
> > No functional behavior changes are intended.
> > 
> > Testing:
> >   - Compiled with W=1
> >   - Build-tested on QEMU x86_64
> > 
> > Feedback and reviews are very welcome.

> It's been about two weeks since the latest posting, and it looks like
> there haven't been any major comments so far atleast on initial changes
> of series. I also don't see any progress on the iio/tesing branch yet.
> 
> Could you please guide me on how you'd like me to take this series forward?
> I'm happy to rework/resend partial/full if needed or wait further.

The recent flood of the patches in IIO makes maintainers and reviewers
overloaded. If you want to help, be a good citizen, start reviewing others'
work. Otherwise, wait when we have time (it make take a few weeks or more).

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-05-18  7:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 17:46 Sanjay Chitroda
2026-05-05 17:46 ` [PATCH v3 01/10] iio: accel: mma8452: handle I2C read error(s) in mma8452_read() Sanjay Chitroda
2026-05-18 13:30   ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 02/10] iio: accel: mma8452: switch to non-devm request_threaded_irq() Sanjay Chitroda
2026-05-06 17:47   ` Jonathan Cameron
2026-05-18 13:31     ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 03/10] iio: accel: mma8452: cleanup codestyle warning Sanjay Chitroda
2026-05-06  9:24   ` Joshua Crofts
2026-05-06 17:53     ` Jonathan Cameron
2026-05-07  7:19       ` Joshua Crofts
2026-05-18 13:32   ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 04/10] iio: accel: mma8452: sort headers alphabetically Sanjay Chitroda
2026-05-06  9:29   ` Joshua Crofts
2026-05-18 13:33     ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 05/10] iio: accel: mma8452: Use dev_err_probe() Sanjay Chitroda
2026-05-05 18:45   ` Joshua Crofts
2026-05-06  9:22     ` Andy Shevchenko
2026-05-06  9:27       ` Joshua Crofts
2026-05-06  9:37         ` Andy Shevchenko
2026-05-18 13:35   ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 06/10] iio: accel: mma8452: convert to bulk regulator usage Sanjay Chitroda
2026-05-05 22:34   ` Joshua Crofts
2026-05-18 13:37     ` Jonathan Cameron
2026-05-06  9:31   ` Andy Shevchenko
2026-05-05 17:46 ` [PATCH v3 07/10] iio: accel: mma8452: use local struct device Sanjay Chitroda
2026-05-06  9:19   ` Joshua Crofts
2026-05-07  2:17     ` Sanjay Chitroda
2026-05-06  9:34   ` Andy Shevchenko
2026-05-05 17:46 ` [PATCH v3 08/10] iio: accel: mma8452: use pm_ptr() and direct runtime PM calls Sanjay Chitroda
2026-05-06  9:42   ` Andy Shevchenko
2026-05-06 18:06   ` Jonathan Cameron
2026-05-07  2:46     ` Sanjay Chitroda
2026-05-07 17:05       ` Jonathan Cameron
2026-05-05 17:46 ` [PATCH v3 09/10] iio: accel: mma8452: Use IIO cleanup helpers Sanjay Chitroda
2026-05-05 17:46 ` [PATCH v3 10/10] iio: accel: mma8452: use guard() to release mutexes Sanjay Chitroda
2026-05-06  9:46   ` Andy Shevchenko
2026-05-06  9:24 ` [PATCH v3 00/10] iio: accel: mma8452: improve coding style, pm and resource cleanup Andy Shevchenko
2026-05-07  2:12   ` Sanjay Chitroda
2026-05-17 20:09 ` Sanjay Chitroda
2026-05-18  7:20   ` Andy Shevchenko [this message]
2026-05-18 13:39     ` 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=agq9uWCrS3txgO5B@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=christoph.muellner@theobroma-systems.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=mfuzzey@parkeon.com \
    --cc=nuno.sa@analog.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sanjayembeddedse@gmail.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

Powered by JetHome