From: Bart Van Assche <bvanassche@acm.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Rupesh Majhi" <zoone.rupert@gmail.com>,
"Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, "Marco Elver" <elver@google.com>,
"Jishnu Prakash" <jishnu.prakash@oss.qualcomm.com>
Subject: Re: [PATCH v3] iio: adc: qcom-spmi-adc5-gen3: fix lock annotations on mutex helpers
Date: Sun, 25 Oct 2026 17:27:47 -0700 [thread overview]
Message-ID: <f151a228-30f9-449a-b71e-7e2ead0ae01f@acm.org> (raw)
In-Reply-To: <20261025215954.73549810@jic23-hlaptop>
On 10/25/26 2:59 PM, Jonathan Cameron wrote:
> I asked that we didn't do this because intent is to follow with
> remaining fixes to be able to enable this IIO tree wide.
> I'd rather avoid the churn of piecewise makefile updates if
> we are going to be there soon.
>
> Rupesh, if you think that is coming soon then please just make
> next version of this the first patch in that series.
>
> If not I don't mind merging this sooner with the makefile change
> to ensure this gets used in the meantime.
As maintainer it is of course your call how to proceed.
In case anyone would be interested in working on a patch series that
annotates all IIO drivers at once, feel free to borrow annotations from
this kernel branch (entirely untested):
https://github.com/bvanassche/linux/tree/thread-safety
That branch has lock context annotations for all drivers in the entire
kernel tree. I'm sending the code from that branch upstream in small
chunks as time permits.
Thanks,
Bart.
next prev parent reply other threads:[~2026-10-26 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 19:15 Rupesh Majhi
2026-10-25 20:10 ` Bart Van Assche
2026-10-25 21:59 ` Jonathan Cameron
2026-10-26 0:27 ` Bart Van Assche [this message]
2026-10-26 8:13 ` Rupesh Majhi
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=f151a228-30f9-449a-b71e-7e2ead0ae01f@acm.org \
--to=bvanassche@acm.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=elver@google.com \
--cc=jic23@kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=zoone.rupert@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
all inboxes | Powered by JetHome®