From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: "Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>, "Lee Jones" <lee@kernel.org>,
"Pavel Machek" <pavel@kernel.org>
Cc: "Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Lukas Timmermann" <linux@timmermann.space>,
"Jan-Simon Moeller" <jansimon.moeller@gmx.de>,
"Riku Voipio" <riku.voipio@iki.fi>,
"Marek Behún" <kabel@kernel.org>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Jonathan Cameron" <jic23@kernel.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] leds: Use named initializers for arrays of i2c_device_data
Date: Fri, 22 May 2026 12:47:08 +0200 [thread overview]
Message-ID: <2a8d1a3c35cf17a4edd202b67be95ab005c61748.camel@gmail.com> (raw)
In-Reply-To: <20260522104222.4081017-2-u.kleine-koenig@baylibre.com>
Hi Uwe,
On Fri, 2026-05-22 at 12:42 +0200, Uwe Kleine-König (The Capable Hub) wrote:
> While being less compact, using named initializers allows to more easily
> see which members of the structs are assigned which value without having
> to lookup the declaration of the struct. And it's also more robust
> against changes to the struct definition.
>
> The mentioned robustness is relevant for a planned change to struct
> i2c_device_id that replaces .driver_data by an anonymous union.
>
> While touching all these arrays, unify usage of whitespace and commas.
>
> This patch doesn't modify the compiled arrays, only their representation
> in source form benefits. The former was confirmed with x86 and arm64
> builds.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
thanks for the re-spin!
Reviewed-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> Hello,
>
> Changes since v1 (available at
> https://lore.kernel.org/linux-leds/20260515163325.471175-2-u.kleine-koenig@baylibre.com):
>
> - s/ / / in leds-lp8501.c
> - also convert drivers/leds/leds-as3668.c which I missed due to not
> having
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b24e1049a5a53f0912046a8f4112d2d43dec74e7
> in my tree.
>
> Thanks to Alexander Sverdlin for pointing these out.
>
> Best regards
> Uwe
> ---
> drivers/leds/flash/leds-as3645a.c | 2 +-
> drivers/leds/flash/leds-lm3601x.c | 4 ++--
> drivers/leds/leds-an30259a.c | 2 +-
> drivers/leds/leds-as3668.c | 2 +-
> drivers/leds/leds-aw200xx.c | 10 +++++-----
> drivers/leds/leds-bd2802.c | 2 +-
> drivers/leds/leds-blinkm.c | 4 ++--
> drivers/leds/leds-is31fl319x.c | 22 +++++++++++-----------
> drivers/leds/leds-is31fl32xx.c | 18 +++++++++---------
> drivers/leds/leds-lm3530.c | 4 ++--
> drivers/leds/leds-lm3532.c | 4 ++--
> drivers/leds/leds-lm355x.c | 6 +++---
> drivers/leds/leds-lm3642.c | 4 ++--
> drivers/leds/leds-lm3692x.c | 4 ++--
> drivers/leds/leds-lm3697.c | 2 +-
> drivers/leds/leds-lp3944.c | 4 ++--
> drivers/leds/leds-lp3952.c | 4 ++--
> drivers/leds/leds-lp50xx.c | 12 ++++++------
> drivers/leds/leds-lp5521.c | 2 +-
> drivers/leds/leds-lp5523.c | 4 ++--
> drivers/leds/leds-lp5562.c | 2 +-
> drivers/leds/leds-lp5569.c | 2 +-
> drivers/leds/leds-lp8501.c | 2 +-
> drivers/leds/leds-lp8860.c | 2 +-
> drivers/leds/leds-lp8864.c | 4 ++--
> drivers/leds/leds-pca9532.c | 8 ++++----
> drivers/leds/leds-pca955x.c | 12 ++++++------
> drivers/leds/leds-pca963x.c | 8 ++++----
> drivers/leds/leds-pca995x.c | 8 ++++----
> drivers/leds/leds-st1202.c | 2 +-
> drivers/leds/leds-tca6507.c | 2 +-
> drivers/leds/leds-tlc591xx.c | 6 +++---
> drivers/leds/leds-turris-omnia.c | 2 +-
> drivers/leds/rgb/leds-ktd202x.c | 6 +++---
> 34 files changed, 91 insertions(+), 91 deletions(-)
--
Alexander Sverdlin.
next prev parent reply other threads:[~2026-05-22 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 10:42 Uwe Kleine-König (The Capable Hub)
2026-05-22 10:47 ` Alexander Sverdlin [this message]
2026-06-04 15:15 ` (subset) " 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=2a8d1a3c35cf17a4edd202b67be95ab005c61748.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=jansimon.moeller@gmx.de \
--cc=jic23@kernel.org \
--cc=kabel@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@timmermann.space \
--cc=pavel@kernel.org \
--cc=riku.voipio@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=u.kleine-koenig@baylibre.com \
/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®