[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82qo9ooo-32q0-2r4r-26q-o8482651qr91@onlyvoer.pbz>
Date: Mon, 25 Jan 2021 13:24:50 -0500 (EST)
From: Nicolas Pitre <npitre@...libre.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Russell King <linux@...linux.org.uk>,
Linux PM <linux-pm@...r.kernel.org>,
linux-clk <linux-clk@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>, Arnd Bergmann <arnd@...db.de>
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@...libre.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
Powered by blists - more mailing lists