[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240627082232.GG2532839@google.com>
Date: Thu, 27 Jun 2024 09:22:32 +0100
From: Lee Jones <lee@...nel.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: linux-leds@...r.kernel.org, kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Christian Marangi <ansuelsmth@...il.com>,
Julia Lawall <julia.lawall@...ia.fr>, Pavel Machek <pavel@....cz>
Subject: Re: [3/3] leds: leds-lp55xx: Convert mutex lock/unlock to guard API
On Thu, 27 Jun 2024, Markus Elfring wrote:
> >>> Convert any entry of mutex lock/unlock to guard API and simplify code.
> >>
> >> Thanks that you would like to support another bit of collateral evolution.
> >>
> >> * Would you get into the mood to benefit any more from applications
> >> of scope-based resource management?
> >
> > Why don't you submit them yourself instead of asking others to do work?
>
> 1. The change resistance (or acceptance) is varying for possible software transformations
> in wide ranges, isn't it?
How would that be any different for anyone else?
Resistance/acceptance should be based on patch quality alone.
> 2. I would appreciate better support and collaboration with additional development resources.
In what regard?
Make the changes and submit them.
What additional resources could you possibly need?
> 3. I hope that further improvements can be achieved also by the means of
> the semantic patch language (Coccinelle software) in safer and more convenient ways.
> Are you looking for any extensions according to the coccicheck tool?
Sounds good. Submit a patch.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists