mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Lee Jones <lee@kernel.org>,
	linux-leds@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christian Marangi <ansuelsmth@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [3/3] leds: leds-lp55xx: Convert mutex lock/unlock to guard API
Date: Thu, 27 Jun 2024 10:12:10 +0200	[thread overview]
Message-ID: <873c2900-859d-40eb-97df-f45f714ed295@web.de> (raw)
In-Reply-To: <20240627070909.GD2532839@google.com>

>>> 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?


2. I would appreciate better support and collaboration with additional development resources.


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?


Regards,
Markus

  reply	other threads:[~2024-06-27  8:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 22:15 [PATCH 1/3] leds: leds-lp5569: Convert to sysfs_emit API Christian Marangi
2024-06-26 22:15 ` [PATCH 2/3] leds: leds-lp5523: " Christian Marangi
2024-06-26 22:15 ` [PATCH 3/3] leds: leds-lp55xx: Convert mutex lock/unlock to guard API Christian Marangi
2024-06-27  5:52   ` Markus Elfring
2024-06-27  7:08     ` Lee Jones
2024-06-27  7:09     ` Lee Jones
2024-06-27  8:12       ` Markus Elfring [this message]
2024-06-27  8:22         ` [3/3] " Lee Jones
2024-06-27  9:24           ` Markus Elfring
2024-07-10  7:10   ` [PATCH 3/3] " Lee Jones
2024-07-10 16:24   ` Markus Elfring
2024-07-10 16:55     ` Lee Jones
2024-07-10 10:29       ` Christian Marangi
2024-07-10 18:10         ` [3/3] " Markus Elfring
2024-07-11  8:08           ` Lee Jones
2024-07-11  8:05         ` [PATCH 3/3] " Lee Jones
2024-07-04 15:44 ` [PATCH 1/3] leds: leds-lp5569: Convert to sysfs_emit API Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873c2900-859d-40eb-97df-f45f714ed295@web.de \
    --to=markus.elfring@web.de \
    --cc=ansuelsmth@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®