[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250329104812225f9ee5@mail.local>
Date: Sat, 29 Mar 2025 11:48:12 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Cc: Markus Elfring <Markus.Elfring@....de>, linux-i3c@...ts.infradead.org,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Bjorn Andersson <andersson@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Konrad Dybcio <konradybcio@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>
Subject: Re: [v2 2/3] i3c: master: Add Qualcomm I3C controller driver
On 29/03/2025 14:38:14+0530, Mukesh Kumar Savaliya wrote:
> Hi Markus,
>
> On 3/29/2025 12:34 AM, Markus Elfring wrote:
> > > > Under which circumstances would you become interested to apply a statement
> > > > like “guard(spinlock_irqsave)(&gi3c->irq_lock);”?
> > > Didn't get, hence a question. Do you suggest to use DEFINE_LOCK_GUARD_1 instead of existing method ?
> > I propose to pick further opportunities up for benefits from scope-based resource management.
> >
> Sorry, still not clear to me what should i add/change ? please share me some
> example.
Don't change anything, Markus is wasting your time.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists