[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7ca4426-8434-4516-9361-c74e73a7f8bd@web.de>
Date: Sat, 5 Oct 2024 21:54:34 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Drew Fustini <dfustini@...storrent.com>, linux-gpio@...r.kernel.org,
linux-riscv@...ts.infradead.org, Fu Wei <wefu@...hat.com>,
Guo Ren <guoren@...nel.org>, Linus Walleij <linus.walleij@...aro.org>
Cc: Drew Fustini <drew@...7.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] pinctrl: th1520: Convert to thp->mutex to guarded
mutex
> Convert th1520_pinctrl_dt_node_to_map() to use guarded mutex for
> thp->mutex.
How does the proposed usage of the programming interface “for_each_available_child_of_node_scoped”
fit to such a change description?
Would you like to omit the first word “to” from the summary phrase?
Would you generally like to increase the application of scope-based resource management
(also in this software area)?
Regards,
Markus
Powered by blists - more mailing lists