From: David Lechner <dlechner@baylibre.com>
To: Rajveer Chaudhari <rajveer.chaudhari.linux@gmail.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: nuno.sa@analog.com, andy@kernel.org, waqar.hameed@axis.com,
linusw@kernel.org, sakari.ailus@linux.intel.com,
harshit.m.mogalapalli@oracle.com, antoniu.miclaus@analog.com,
andrew.ijano@gmail.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] iio: accel: sca3000: convert to guard(mutex)
Date: Mon, 9 Mar 2026 15:03:23 -0500 [thread overview]
Message-ID: <b1aa81e6-ec3f-45cd-84db-e26c465ae267@baylibre.com> (raw)
In-Reply-To: <CANS1UbiJgvbbzOAbi1TM5=N-Gj-LQoOFRyBUf06qkZRY3zw+Sw@mail.gmail.com>
On 3/9/26 2:58 PM, Rajveer Chaudhari wrote:
> Hello Jonathan,
>
> Thanks for the review, I will add all of your suggested return path,
> indentation fixes in v3.
>
> But I have a question, should I submit the next version of patch right
> now as you reviewed
> the whole patch, or wait for 24 hrs as instructed by Andy Shevchenko
> to let others
> have a chance to comment, review.
Waiting even longer than 24 hours is better. Not everyone has time to
review every day. Ideally, wait 1 week between revisions. If it is something
urgent, it can be sooner. Converting things to guard() is certainly not
urgent.
next prev parent reply other threads:[~2026-03-09 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 15:34 [PATCH v2 0/4] iio: accel: convert to guard(mutex) Rajveer Chaudhari
2026-03-09 15:34 ` [PATCH v2 1/4] iio: accel: bmc150: " Rajveer Chaudhari
2026-03-09 16:28 ` Andy Shevchenko
2026-03-09 19:15 ` Jonathan Cameron
2026-03-09 19:13 ` Jonathan Cameron
2026-03-09 15:34 ` [PATCH v2 2/4] iio: accel: mma8452: " Rajveer Chaudhari
2026-03-09 15:34 ` [PATCH v2 3/4] iio: accel: mma9551: " Rajveer Chaudhari
2026-03-09 15:34 ` [PATCH v2 4/4] iio: accel: sca3000: " Rajveer Chaudhari
2026-03-09 19:30 ` Jonathan Cameron
2026-03-09 19:58 ` Rajveer Chaudhari
2026-03-09 20:03 ` David Lechner [this message]
2026-03-09 20:06 ` Rajveer Chaudhari
2026-03-09 16:30 ` [PATCH v2 0/4] iio: accel: " Andy Shevchenko
2026-03-09 17:33 ` Rajveer Chaudhari
2026-03-09 17:57 ` Waqar Hameed
2026-03-09 18:15 ` Rajveer Chaudhari
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=b1aa81e6-ec3f-45cd-84db-e26c465ae267@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andrew.ijano@gmail.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jic23@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rajveer.chaudhari.linux@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=waqar.hameed@axis.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