From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: "Bartosz Golaszewski" <brgl@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"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 12:20:10 +0200 [thread overview]
Message-ID: <agw5WgpA0ul3jith@shikoro> (raw)
In-Reply-To: <agwvkt_iWF9UUR-t@monoceros>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
Hi,
I missed Bart's original mail, yet...
> > > 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/?).
Good idea!
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-19 10:20 UTC|newest]
Thread overview: 5+ 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)
2026-05-19 9:45 ` Arnd Bergmann
2026-05-19 10:20 ` Wolfram Sang [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=agw5WgpA0ul3jith@shikoro \
--to=wsa+renesas@sang-engineering.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 \
--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 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.