Messages in this thread | | | Date | Mon, 25 Jan 2021 13:24:50 -0500 (EST) | From | Nicolas Pitre <> | Subject | Re: [PATCH v3] PM / clk: make PM clock layer compatible with clocks that must sleep |
| |
On Mon, 25 Jan 2021, Rafael J. Wysocki wrote:
> On Sun, Jan 24, 2021 at 12:07 AM Nicolas Pitre <npitre@baylibre.com> wrote: > > A note on sparse: > > According to https://lwn.net/Articles/109066/ there are things > > that sparse can't cope with. In particular, pm_clk_op_lock() and > > pm_clk_op_unlock() may or may not lock/unlock psd->lock depending on > > some runtime condition. To work around that we tell sparse the lock > > is always untaken for the purpose of static analisys. > > It looks like sparse is still complaining: > > https://lore.kernel.org/linux-acpi/600dc681.3mAl9WQXnragfNZk%25lkp@intel.com/
Would you happen to still have one of those randconfig configuration?
I'd like to know why sparse complains about 3 out of 93 configs.
Nicolas
| |