All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=28The_Capable_Hub=29_=3Cu=2Ekleine-koenig?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	=?utf-8?q?=40baylibre=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, sre@kernel.org,
	visitorckw@gmail.com, bleung@chromium.org, groeck@chromium.org,
	linux@weissschuh.net, krzk@kernel.org, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	chrome-platform@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, hansg@kernel.org,
	m.szyprowski@samsung.com, sebastian.krzyszkowiak@puri.sm,
	kernel@puri.sm, dlan@kernel.org, andreas@kemnade.info,
	mazziesaccount@gmail.com, sven@kernel.org, j@jannau.net,
	neal@gompa.dev, amitsd@google.com, samkay014@gmail.com,
	spacemit@lists.linux.dev, asahi@lists.linux.dev,
	imx@lists.linux.dev, wens@kernel.org
Subject: Re: [PATCH v1 0/6] power: Use named initializers for platform_device_id arrays
Date: Fri, 26 Jun 2026 08:20:56 +0000	[thread overview]
Message-ID: <178246205698.3816447.10450599511697138681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1780048925.git.u.kleine-koenig@baylibre.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sebastian Reichel <sebastian.reichel@collabora.com>:

On Fri, 29 May 2026 12:18:15 +0200 you wrote:
> Hello,
> 
> this series targets to use named initializers for platform_device_id
> arrays. In general these are better readable for humans and more robust
> to changes in the respective struct definition.
> 
> This robustness is needed as I want to do
> 
> [...]

Here is the summary with links:
  - [v1,4/6] power: Use named initializers for platform_device_id arrays
    https://git.kernel.org/riscv/c/e28f7498dd81

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=28The_Capable_Hub=29_=3Cu=2Ekleine-koenig?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	=?utf-8?q?=40baylibre=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, sre@kernel.org,
	visitorckw@gmail.com, bleung@chromium.org, groeck@chromium.org,
	linux@weissschuh.net, krzk@kernel.org, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	chrome-platform@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, hansg@kernel.org,
	m.szyprowski@samsung.com, sebastian.krzyszkowiak@puri.sm,
	kernel@puri.sm, dlan@kernel.org, andreas@kemnade.info,
	mazziesaccount@gmail.com, sven@kernel.org, j@jannau.net,
	neal@gompa.dev, amitsd@google.com, samkay014@gmail.com,
	spacemit@lists.linux.dev, asahi@lists.linux.dev,
	imx@lists.linux.dev, wens@kernel.org
Subject: Re: [PATCH v1 0/6] power: Use named initializers for platform_device_id arrays
Date: Fri, 26 Jun 2026 08:20:56 +0000	[thread overview]
Message-ID: <178246205698.3816447.10450599511697138681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1780048925.git.u.kleine-koenig@baylibre.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sebastian Reichel <sebastian.reichel@collabora.com>:

On Fri, 29 May 2026 12:18:15 +0200 you wrote:
> Hello,
> 
> this series targets to use named initializers for platform_device_id
> arrays. In general these are better readable for humans and more robust
> to changes in the respective struct definition.
> 
> This robustness is needed as I want to do
> 
> [...]

Here is the summary with links:
  - [v1,4/6] power: Use named initializers for platform_device_id arrays
    https://git.kernel.org/riscv/c/e28f7498dd81

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-06-26  8:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 10:18 [PATCH v1 0/6] power: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18 ` Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18 ` [PATCH v1 1/6] power: Drop unused assignment of platform_device_id driver data Uwe Kleine-König (The Capable Hub)
2026-05-29 22:02   ` Tzung-Bi Shih
2026-05-29 10:18 ` [PATCH v1 2/6] power: supply: max14577: Drop driver data in of and platform device id arrays Uwe Kleine-König (The Capable Hub)
2026-05-29 14:20   ` Krzysztof Kozlowski
2026-05-29 10:18 ` [PATCH v1 3/6] power: supply: max17042: " Uwe Kleine-König (The Capable Hub)
2026-05-29 14:17   ` Krzysztof Kozlowski
2026-05-29 14:21   ` Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18 ` [PATCH v1 4/6] power: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18   ` Uwe Kleine-König (The Capable Hub)
2026-05-29 11:02   ` sashiko-bot
2026-06-26 13:58     ` Uwe Kleine-König
2026-05-29 11:29   ` Joshua Peisach
2026-05-29 11:29     ` Joshua Peisach
2026-05-29 18:49     ` Uwe Kleine-König (The Capable Hub)
2026-05-29 18:49       ` Uwe Kleine-König (The Capable Hub)
2026-06-01  6:48   ` Matti Vaittinen
2026-06-01  6:48     ` Matti Vaittinen
2026-05-29 10:18 ` [PATCH v1 5/6] power: supply: mt6360_charger: Use of match table unconditionally Uwe Kleine-König (The Capable Hub)
2026-05-29 10:18 ` [PATCH v1 6/6] power: Unify code style for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-30 15:34   ` Chen-Yu Tsai
2026-06-03 20:46 ` (subset) [PATCH v1 0/6] power: Use named initializers " Sebastian Reichel
2026-06-03 20:46   ` Sebastian Reichel
2026-06-26  8:20 ` patchwork-bot+linux-riscv [this message]
2026-06-26  8:20   ` patchwork-bot+linux-riscv

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=178246205698.3816447.10450599511697138681.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?q?=40baylibre=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=28The_Capable_Hub=29_=3Cu=2Ekleine-koenig?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=amitsd@google.com \
    --cc=andreas@kemnade.info \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=asahi@lists.linux.dev \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dlan@kernel.org \
    --cc=groeck@chromium.org \
    --cc=hansg@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=j@jannau.net \
    --cc=kernel@puri.sm \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@weissschuh.net \
    --cc=m.szyprowski@samsung.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mazziesaccount@gmail.com \
    --cc=neal@gompa.dev \
    --cc=samkay014@gmail.com \
    --cc=sebastian.krzyszkowiak@puri.sm \
    --cc=spacemit@lists.linux.dev \
    --cc=sre@kernel.org \
    --cc=sven@kernel.org \
    --cc=visitorckw@gmail.com \
    --cc=wens@kernel.org \
    /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.