From: Jonathan Cameron <jic23@kernel•org>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre•com>
Cc: "Chen-Yu Tsai" <wens@kernel•org>,
"Duje Mihanović" <duje@dujemihanovic•xyz>,
"David Lechner" <dlechner@baylibre•com>,
"Nuno Sá" <nuno.sa@analog•com>,
"Andy Shevchenko" <andy@kernel•org>,
"Jernej Skrabec" <jernej.skrabec@gmail•com>,
"Samuel Holland" <samuel@sholland•org>,
"Wolfram Sang" <wsa+renesas@sang-engineering•com>,
"Sakari Ailus" <sakari.ailus@linux•intel.com>,
linux-iio@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-sunxi@lists•linux.dev
Subject: Re: [PATCH v1] iio: Use named initializers for platform_device_id arrays
Date: Thu, 28 May 2026 12:58:24 +0100 [thread overview]
Message-ID: <20260528125824.0f5f9853@jic23-huawei> (raw)
In-Reply-To: <1a45a4aade700448d7b1c702210ff147aaf21f90.1779962510.git.u.kleine-koenig@baylibre.com>
On Thu, 28 May 2026 12:16:49 +0200
Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre•com> wrote:
> Named initializers are better readable and more robust to changes of the
> struct definition. This robustness is relevant for a planned change to
> struct platform_device_id replacing .driver_data by an anonymous union.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre•com>
Applied.
thanks,
Jonathan
prev parent reply other threads:[~2026-05-28 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 10:16 [PATCH v1] iio: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-28 11:58 ` Jonathan Cameron [this message]
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=20260528125824.0f5f9853@jic23-huawei \
--to=jic23@kernel$(echo .)org \
--cc=andy@kernel$(echo .)org \
--cc=dlechner@baylibre$(echo .)com \
--cc=duje@dujemihanovic$(echo .)xyz \
--cc=jernej.skrabec@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-iio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-sunxi@lists$(echo .)linux.dev \
--cc=nuno.sa@analog$(echo .)com \
--cc=sakari.ailus@linux$(echo .)intel.com \
--cc=samuel@sholland$(echo .)org \
--cc=u.kleine-koenig@baylibre$(echo .)com \
--cc=wens@kernel$(echo .)org \
--cc=wsa+renesas@sang-engineering$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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