From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Bartosz Golaszewski <brgl@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Eric Piel" <eric.piel@tremplin-utc.net>,
"Naveen Krishna Chatradhi" <naveenkrishna.chatradhi@amd.com>,
"Akshay Gupta" <Akshay.Gupta@amd.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Abd-Alrhman Masalkhi" <abd.masalkhi@gmail.com>,
"Chen Ni" <nichen@iscas.ac.cn>, "Kees Cook" <kees@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v1] misc: Use named initializers for arrays of i2c_device_data
Date: Tue, 19 May 2026 11:40:37 +0200 [thread overview]
Message-ID: <agwvkt_iWF9UUR-t@monoceros> (raw)
In-Reply-To: <CAMRc=MfxgY77TozGqUsWrjsTmBKnZLm0dziAn1JAiTok67RXnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Mon, May 18, 2026 at 09:53:08AM +0200, Bartosz Golaszewski wrote:
> On Fri, May 15, 2026 at 6:27 PM Uwe Kleine-König (The Capable Hub)
> <u.kleine-koenig@baylibre.com> wrote:
> > drivers/misc/eeprom/at24.c | 62 +++++++-------
>
> This drivers lives under drivers/misc/ but I maintain it separately
> and send PRs to Wolfram so they go through the i2c tree (historical
> reasons really and maybe we should move it under drivers/nvmem/?). Can
> you send this separately?
Done
(https://lore.kernel.org/linux-i2c/20260519093806.1567914-2-u.kleine-koenig@baylibre.com).
@Arnd + @Greg: Should I split off still more or is a single patch for
the remainder of drivers/misc fine?
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-19 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:27 [PATCH v1] misc: Use named initializers for arrays of i2c_device_data Uwe Kleine-König (The Capable Hub)
2026-05-18 7:53 ` Bartosz Golaszewski
2026-05-19 9:40 ` Uwe Kleine-König (The Capable Hub) [this message]
2026-05-19 9:45 ` Arnd Bergmann
2026-06-10 17:19 ` Uwe Kleine-König
2026-05-19 10:20 ` Wolfram Sang
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=agwvkt_iWF9UUR-t@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=Akshay.Gupta@amd.com \
--cc=abd.masalkhi@gmail.com \
--cc=arnd@arndb.de \
--cc=brgl@kernel.org \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linux@weissschuh.net \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=nichen@iscas.ac.cn \
/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