From: Markus Elfring <Markus.Elfring@web.de>
To: Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>,
linux-leds@vger.kernel.org, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] leds: Add LED1202 I2C driverr
Date: Sun, 21 Jul 2024 15:55:12 +0200 [thread overview]
Message-ID: <52544eec-60d0-42fa-bdb0-ffe56627c426@web.de> (raw)
In-Reply-To: <ZpzkBM_ZwM8hdwgP@admins-MacBook-Air.local>
> The LED1202 is a 12-channel low quiescent current LED driver.
…
1. How do you think about to improve such a change description with imperative wordings?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10#n94
2. Would you like to avoid a typo in the summary phrase?
…
> +++ b/drivers/leds/leds-st1202.c
> @@ -0,0 +1,899 @@
…
> +#define ST1202_LED_CHANNEL_10 10
> +#define ST1202_LED_CHANNEL_11 11
> +#define ST1202_MAX_LEDS 12
…
> +#define ST1202_PATTERN_6 6
> +#define ST1202_PATTERN_7 7
> +#define ST1202_PATTERNS_NR 8
Can such identifiers be a bit nicer as part of enumerations?
…
> +static ssize_t st1202_patt_seq_rep_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
…
> + chip = dev_get_drvdata(dev);
> +
> + mutex_lock(&chip->lock);
…
> + mutex_unlock(&chip->lock);
…
Under which circumstances would you become interested to apply a statement
like “guard(mutex)(&chip->lock);”?
https://elixir.bootlin.com/linux/v6.10/source/include/linux/mutex.h#L196
Regards,
Markus
next prev parent reply other threads:[~2024-07-21 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 10:33 Vicentiu Galanopulo
2024-07-21 13:55 ` Markus Elfring [this message]
2024-07-22 7:03 ` Pavel Machek
2024-07-21 14:08 ` Christophe JAILLET
2024-07-22 7:06 ` Pavel Machek
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=52544eec-60d0-42fa-bdb0-ffe56627c426@web.de \
--to=markus.elfring@web.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=vicentiu.galanopulo@remote-tech.co.uk \
/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®