From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Hans de Goede" <hansg@kernel.org>,
"Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Pengyu Luo <mitltlatltl@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] platform: arm64 Use named initializers for struct i2c_device_id
Date: Thu, 28 May 2026 15:11:08 +0300 [thread overview]
Message-ID: <177997026863.9687.18087862956657914467.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260519144341.1589034-2-u.kleine-koenig@baylibre.com>
On Tue, 19 May 2026 16:43:41 +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.
>
> This patch doesn't modify the compiled arrays, only their representation
> in source form benefits. The former was confirmed with x86 and arm64
> builds.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform: arm64 Use named initializers for struct i2c_device_id
commit: fbab18baaf9a3fe45c6fd75dab7f5b7f6992356f
--
i.
prev parent reply other threads:[~2026-05-28 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 14:43 Uwe Kleine-König (The Capable Hub)
2026-05-20 8:04 ` Bryan O'Donoghue
2026-05-28 12:11 ` Ilpo Järvinen [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=177997026863.9687.18087862956657914467.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bryan.odonoghue@linaro.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@kernel.org \
--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®