From: patchwork-bot+chrome-platform@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org
Cc: a.zummo@towertech.it, alexandre.belloni@bootlin.com,
linus.walleij@linaro.org, nicolas.ferre@microchip.com,
claudiu.beznea@microchip.com, f.fainelli@gmail.com,
bleung@chromium.org, kumba@gentoo.org, ulli.kroll@googlemail.com,
vz@mleia.com, cw00.choi@samsung.com,
krzysztof.kozlowski@linaro.org, conor.dooley@microchip.com,
daire.mcnamara@microchip.com, eddie.huang@mediatek.com,
sean.wang@mediatek.com, matthias.bgg@gmail.com,
miquel.raynal@bootlin.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, vincent.sunplus@gmail.com,
thierry.reding@gmail.com, jonathanh@nvidia.com,
michal.simek@xilinx.com, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com, groeck@chromium.org,
chrome-platform@lists.linux.dev, linux-riscv@lists.infradead.org,
angelogioacchino.delregno@collabora.com,
linux-mediatek@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-tegra@vger.kernel.org, patches@opensource.cirrus.com,
kernel@pengutronix.de
Subject: Re: [PATCH 00/41] rtc: Convert to platform remove callback returning void
Date: Mon, 08 May 2023 03:45:14 +0000 [thread overview]
Message-ID: <168351751423.5651.18106995341642882418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230304133028.2135435-1-u.kleine-koenig@pengutronix.de>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Alexandre Belloni <alexandre.belloni@bootlin.com>:
On Sat, 4 Mar 2023 14:29:47 +0100 you wrote:
> Hello,
>
> this patch series adapts the platform drivers below drivers/rtc to use the
> .remove_new() callback. Compared to the traditional .remove() callback
> .remove_new() returns no value. This is a good thing because the driver core
> doesn't (and cannot) cope for errors during remove. The only effect of a
> non-zero return value in .remove() is that the driver core emits a warning. The
> device is removed anyhow and an early return from .remove() usually yields a
> resource leak.
>
> [...]
Here is the summary with links:
- [10/41] rtc: cros-ec: Convert to platform remove callback returning void
https://git.kernel.org/chrome-platform/c/0d8742e61098
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-05-08 3:45 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 13:29 [PATCH 00/41] rtc: Convert to platform remove callback returning void Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 01/41] rtc: 88pm80x: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 02/41] rtc: 88pm860x: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 03/41] rtc: ab8500: " Uwe Kleine-König
2023-03-07 13:35 ` Linus Walleij
2023-03-04 13:29 ` [PATCH 04/41] rtc: ac100: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 05/41] rtc: asm9260: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 06/41] rtc: at91sam9: " Uwe Kleine-König
2023-03-06 11:55 ` Claudiu.Beznea
2023-03-04 13:29 ` [PATCH 07/41] rtc: brcmstb-waketimer: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 08/41] rtc: cadence: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 09/41] rtc: cmos: " Uwe Kleine-König
2023-03-04 13:29 ` [PATCH 10/41] rtc: cros-ec: " Uwe Kleine-König
2023-03-07 5:30 ` Tzung-Bi Shih
2023-03-04 13:29 ` [PATCH 11/41] rtc: ds1685: " Uwe Kleine-König
2023-03-06 19:43 ` Joshua Kinard
2023-03-06 21:22 ` Uwe Kleine-König
2023-03-07 2:09 ` Joshua Kinard
2023-03-07 8:11 ` Uwe Kleine-König
2023-03-08 16:20 ` Joshua Kinard
2023-03-08 16:47 ` Uwe Kleine-König
2023-03-13 15:08 ` Joshua Kinard
2023-03-04 13:29 ` [PATCH 12/41] rtc: ftrtc010: " Uwe Kleine-König
2023-03-07 13:35 ` Linus Walleij
2023-03-04 13:30 ` [PATCH 13/41] rtc: hid-sensor-time: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 14/41] rtc: lpc24xx: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 15/41] rtc: max77686: " Uwe Kleine-König
2023-03-05 9:50 ` Krzysztof Kozlowski
2023-03-04 13:30 ` [PATCH 16/41] rtc: mc13xxx: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 17/41] rtc: mpc5121: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 18/41] rtc: mpfs: " Uwe Kleine-König
2023-03-04 13:47 ` Conor Dooley
2023-03-04 13:30 ` [PATCH 19/41] rtc: mt7622: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 20/41] rtc: mxc_v2: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 21/41] rtc: omap: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 22/41] rtc: palmas: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 23/41] rtc: pcf50633: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 24/41] rtc: pic32: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 25/41] rtc: pm8xxx: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 26/41] rtc: rc5t583: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 27/41] rtc: rtd119x: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 28/41] rtc: rzn1: " Uwe Kleine-König
2023-03-06 8:12 ` Miquel Raynal
2023-03-04 13:30 ` [PATCH 29/41] rtc: s3c: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 30/41] rtc: sa1100: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 31/41] rtc: spear: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 32/41] rtc: stm32: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 33/41] rtc: stmp3xxx: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 34/41] rtc: sunplus: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 35/41] rtc: tegra: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 36/41] rtc: tps6586x: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 37/41] rtc: twl: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 38/41] rtc: vt8500: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 39/41] rtc: wm8350: " Uwe Kleine-König
2023-03-06 9:37 ` Charles Keepax
2023-03-04 13:30 ` [PATCH 40/41] rtc: xgene: " Uwe Kleine-König
2023-03-04 13:30 ` [PATCH 41/41] rtc: zynqmp: " Uwe Kleine-König
2023-03-14 9:05 ` [PATCH 00/41] rtc: " Naresh Kamboju
2023-03-17 22:09 ` Alexandre Belloni
2023-05-08 3:45 ` patchwork-bot+chrome-platform [this message]
2023-05-08 3:56 ` patchwork-bot+chrome-platform
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=168351751423.5651.18106995341642882418.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=claudiu.beznea@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=cw00.choi@samsung.com \
--cc=daire.mcnamara@microchip.com \
--cc=eddie.huang@mediatek.com \
--cc=f.fainelli@gmail.com \
--cc=groeck@chromium.org \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kumba@gentoo.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-tegra@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=patches@opensource.cirrus.com \
--cc=sean.wang@mediatek.com \
--cc=thierry.reding@gmail.com \
--cc=ulli.kroll@googlemail.com \
--cc=vincent.sunplus@gmail.com \
--cc=vz@mleia.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).