From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: "Anshul Dalal" <anshulusr@gmail.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Yassine Oudjana" <y.oudjana@protonmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Support Opensource" <support.opensource@diasemi.com>,
"Nick Dyer" <nick@shmanahar.org>,
"Hans de Goede" <hansg@kernel.org>,
"Job Noorman" <job@noorman.info>,
"Mika Penttilä" <mpenttil@redhat.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Kees Cook" <kees@kernel.org>,
"bui duc phuc" <phucduc.bui@gmail.com>,
"Thorsten Blum" <thorsten.blum@linux.dev>,
"Yauhen Kharuzhy" <jekhor@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Marco Crivellari" <marco.crivellari@suse.com>,
"Minseong Kim" <ii4gsp@gmail.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Oleh Kuzhylnyi" <kuzhylol@gmail.com>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Josua Mayer" <josua@solid-run.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Jeff LaBundy" <jeff@labundy.com>,
"Javier Carrasco" <javier.carrasco@wolfvision.net>,
"David Heidelberg" <david@ixit.cz>,
"Petr Hodina" <petr.hodina@protonmail.com>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"Johannes Kirchmair" <johannes.kirchmair@skidata.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Xichao Zhao" <zhao.xichao@vivo.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
platform-driver-x86@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v1] Input: Use named initializers for arrays of i2c_device_data
Date: Sat, 30 May 2026 22:13:47 -0700 [thread overview]
Message-ID: <ahvDNu0TQKtjvmSk@google.com> (raw)
In-Reply-To: <ahrP4STTFdUsBp0O@monoceros>
On Sat, May 30, 2026 at 02:02:20PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Hello Dmitry,
>
> On Fri, May 29, 2026 at 10:56:48PM -0700, Dmitry Torokhov wrote:
> > I like the ability to properly set up pointers for driver data, however
> > I do not think we should use named initializers for name field. As long
> > as we are not planning on moving its position I like the brevity of just
> > saying
> >
> > { "ili210x", .driver_data_ptr = &ili210x_chip },
> >
> > Can we keep the old style for the name field?
>
> I have no strong opinion here, my patch introduces the named initializer
> for both members for consistency. Note that my patches for all the other
> subsystems (and also other *_device_id) do the same and you're the first
> maintainer with that expressed preference.
>
> I even sent a few patches that adapt initializers without .driver_data
> (e.g.
> https://lore.kernel.org/all/177932943265.3832404.360063047381979287.git-patchwork-notify@kernel.org/)
> that got positive feedback so far.
>
> So if you're ok with having input differ in style from (up to now) all
> other subsystems, I can rework the patch.
OK, I guess I am too late to voice my opinion. I do not want to have
different style, in this particular case at least, so I applied the
patch.
Thanks.
--
Dmitry
prev parent reply other threads:[~2026-05-31 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:48 [PATCH v1] Input: Use named initializers for arrays of i2c_device_data Uwe Kleine-König (The Capable Hub)
2026-05-15 16:53 ` sashiko-bot
2026-05-18 7:24 ` Geert Uytterhoeven
2026-05-18 7:30 ` Andy Shevchenko
2026-05-18 7:56 ` Uwe Kleine-König (The Capable Hub)
2026-05-30 5:56 ` Dmitry Torokhov
2026-05-30 12:02 ` Uwe Kleine-König (The Capable Hub)
2026-05-31 5:13 ` Dmitry Torokhov [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=ahvDNu0TQKtjvmSk@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshulusr@gmail.com \
--cc=clamor95@gmail.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=david@ixit.cz \
--cc=geert+renesas@glider.be \
--cc=hansg@kernel.org \
--cc=ii4gsp@gmail.com \
--cc=javier.carrasco@wolfvision.net \
--cc=jeff@labundy.com \
--cc=jekhor@gmail.com \
--cc=job@noorman.info \
--cc=johannes.kirchmair@skidata.com \
--cc=josua@solid-run.com \
--cc=kees@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuzhylol@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=m.tretter@pengutronix.de \
--cc=marco.crivellari@suse.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.hennerich@analog.com \
--cc=mingo@kernel.org \
--cc=mpenttil@redhat.com \
--cc=nick@shmanahar.org \
--cc=nicolas.ferre@microchip.com \
--cc=petr.hodina@protonmail.com \
--cc=phucduc.bui@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=support.opensource@diasemi.com \
--cc=tglx@kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=u.kleine-koenig@baylibre.com \
--cc=y.oudjana@protonmail.com \
--cc=zhao.xichao@vivo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.