[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08d9a783-2de1-4658-b617-5e6e6947ac2b@web.de>
Date: Fri, 6 Sep 2024 21:05:44 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Dikshita Agarwal <quic_dikshita@...cinc.com>,
linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org, Abhinav Kumar <quic_abhinavk@...cinc.com>,
Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Mauro Carvalho Chehab <mchehab@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>, Rob Herring <robh@...nel.org>,
Vikash Garodia <quic_vgarodia@...cinc.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 05/29] media: iris: implement iris v4l2 file ops
…
> +++ b/drivers/media/platform/qcom/iris/iris_vidc.c
> @@ -0,0 +1,174 @@
…
> ++int iris_close(struct file *filp)
> +{
…
> + mutex_lock(&inst->lock);
> + iris_v4l2_fh_deinit(inst);
> + mutex_unlock(&inst->lock);
…
Under which circumstances would you become interested to apply a statement
like “guard(mutex)(&inst->lock);”?
https://elixir.bootlin.com/linux/v6.11-rc6/source/include/linux/mutex.h#L196
Regards,
Markus
Powered by blists - more mailing lists