[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60c5504d-341f-4ce5-b337-1eca92a9506f@web.de>
Date: Fri, 7 Feb 2025 07:39:03 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Bjorn Helgaas <helgaas@...nel.org>,
Thippeswamy Havalige <thippeswamy.havalige@....com>,
linux-pci@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
devicetree@...r.kernel.org, Rob Herring <robh@...nel.org>,
Bharat Kumar Gogada <bharat.kumar.gogada@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Conor Dooley <conor+dt@...nel.org>,
Jingoo Han <jingoohan1@...il.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Michal Simek <michal.simek@....com>, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [v8 3/3] PCI: amd-mdb: Add AMD MDB Root Port driver
> I don't *really* like guard() anyway because it's kind of magic in
> that the unlock doesn't actually appear in the code, and it's kind of
> hard to unravel what guard() is and how it works. But I guess that's
> mostly because it's just a new idiom that takes time to internalize.
How will the circumstances evolve further for growing applications of
scope-based resource management?
Regards,
Markus
Powered by blists - more mailing lists