[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e32324c8-1888-451b-8621-0e468ca61fd9@web.de>
Date: Fri, 28 Mar 2025 20:04:56 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>,
linux-i3c@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
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
>> 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.
Regards,
Markus
Powered by blists - more mailing lists