From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40baylibre=2Ecom=3E?=@ci.codeaurora.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew@lunn.ch, f.fainelli@gmail.com,
olteanv@gmail.com, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, george.mccollister@gmail.com,
idosch@nvidia.com, petrm@nvidia.com, jk@codeconstruct.com.au,
matt@codeconstruct.com.au, o.rempel@pengutronix.de,
kory.maincent@bootlin.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: Drop explicit initialization of struct i2c_device_id::driver_data to 0
Date: Wed, 26 Jun 2024 14:40:29 +0000 [thread overview]
Message-ID: <171941282978.9808.3649469008264341115.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240625083853.2205977-2-u.kleine-koenig@baylibre.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Jun 2024 10:38:53 +0200 you wrote:
> These drivers don't use the driver_data member of struct i2c_device_id,
> so don't explicitly initialize this member.
>
> This prepares putting driver_data in an anonymous union which requires
> either no initialization or named designators. But it's also a nice
> cleanup on its own.
>
> [...]
Here is the summary with links:
- [net-next] net: Drop explicit initialization of struct i2c_device_id::driver_data to 0
https://git.kernel.org/netdev/net-next/c/a6a6a9809411
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-26 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 8:38 [PATCH net-next] net: Drop explicit initialization of struct i2c_device_id::driver_data to 0 Uwe Kleine-König
2024-06-25 9:04 ` Petr Machata
2024-06-25 9:50 ` Kory Maincent
2024-06-25 23:56 ` Jeremy Kerr
2024-06-26 5:00 ` Oleksij Rempel
2024-06-26 14:40 ` patchwork-bot+netdevbpf [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=171941282978.9808.3649469008264341115.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40baylibre=2Ecom=3E?=@ci.codeaurora.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=idosch@nvidia.com \
--cc=jk@codeconstruct.com.au \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=woojung.huh@microchip.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;
as well as URLs for NNTP newsgroup(s).