Linux IIO development
 help / color / mirror / Atom feed
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Joshua Crofts <joshua.crofts1@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 07/10] iio: accel: mma8452: use local struct device
Date: Thu, 07 May 2026 07:47:05 +0530	[thread overview]
Message-ID: <CCC9ECD1-6847-4AE1-9176-57B1F8F84EF4@gmail.com> (raw)
In-Reply-To: <CALoEA-y37XZMVSnzdUbmWKHOWxs5r=39DEVcs_G71vEQTZ=ntA@mail.gmail.com>



On 6 May 2026 2:49:33 pm IST, Joshua Crofts <joshua.crofts1@gmail.com> wrote:
>On Tue, 5 May 2026 at 19:50, Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
>> @@ -1552,7 +1552,7 @@ static int mma8452_probe(struct i2c_client *client)
>>         struct iio_dev *indio_dev;
>>         int ret;
>
>As mentioned, you added the local struct device in patch 5, making
>this really confusing (and potentially breaking if only a partial set
>of the patches would be picked up). Please add it here.
Hi Joshua,

Thank you for the review.
I have prepared series as there is some dependency on earlier change with respect to current. If we pick random change it has high changes to fail.

FYI, compilation is validated on each change so if someone take few initial patch then hopefully nothing would break. Additionally, if we plan to take random patches from series based on some review comment or requirement then I would resend new series specific to that patches to avoid any break.

>

  reply	other threads:[~2026-05-07  2:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 17:46 [PATCH v3 00/10] iio: accel: mma8452: improve coding style, pm and resource cleanup 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-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-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-05 17:46 ` [PATCH v3 04/10] iio: accel: mma8452: sort headers alphabetically Sanjay Chitroda
2026-05-06  9:29   ` Joshua Crofts
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-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-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 [this message]
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

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=CCC9ECD1-6847-4AE1-9176-57B1F8F84EF4@gmail.com \
    --to=sanjayembeddedse@gmail.com \
    --cc=andy@kernel.org \
    --cc=christoph.muellner@theobroma-systems.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=joshua.crofts1@gmail.com \
    --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 \
    /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