From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: linux-rtc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-riscv@lists.infradead.org, Peng Fan <peng.fan@nxp.com>,
Antonio Borneo <antonio.borneo@foss.st.com>
Subject: Re: [PATCH 0/7] rtc: Use devm_pm_set_wake_irq to simplify code
Date: Mon, 3 Mar 2025 22:53:09 +0100 [thread overview]
Message-ID: <174103876909.1106916.958645902819103595.b4-ty@bootlin.com> (raw)
In-Reply-To: <20250205-rtc-cleanup-v1-0-66165678e089@nxp.com>
On Wed, 05 Feb 2025 08:58:18 +0800, Peng Fan (OSS) wrote:
> This is a pick-up of patch 6-12 from patchset [1]
>
> Since devm_pm_set_wake_irq is in 6.14, so resend the rtc parts.
>
> R-b tags from Linus Walleij and Antonio Borneo are still kept.
>
> [1] https://lore.kernel.org/all/CAJZ5v0jb=0c5m=FeA-W-aG30H4706Ay_xCHTsiC1S-7MuGxqTQ@mail.gmail.com/#r
>
> [...]
Applied, thanks!
[1/7] rtc: stm32: Use resource managed API to simplify code
https://git.kernel.org/abelloni/c/04572d18921d
[2/7] rtc: nxp-bbnsm: Use resource managed API to simplify code
https://git.kernel.org/abelloni/c/6b296dee3eb7
[3/7] rtc: ds1343: Use devm_pm_set_wake_irq
https://git.kernel.org/abelloni/c/5ad218f101e4
[4/7] rtc: pm8xxx: Use devm_pm_set_wake_irq
https://git.kernel.org/abelloni/c/e8a0b6e62429
[5/7] rtc: ab8500: Use resource managed API to simplify code
https://git.kernel.org/abelloni/c/ca36c9301117
[6/7] rtc: mpfs: Use devm_pm_set_wake_irq
https://git.kernel.org/abelloni/c/d8690ce183bb
[7/7] rtc: pl031: Use resource managed API to simplify code
https://git.kernel.org/abelloni/c/90e0bcc9392d
Best regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-03-03 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 0:58 Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 1/7] rtc: stm32: Use resource managed API " Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 2/7] rtc: nxp-bbnsm: " Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 3/7] rtc: ds1343: Use devm_pm_set_wake_irq Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 4/7] rtc: pm8xxx: " Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 5/7] rtc: ab8500: Use resource managed API to simplify code Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 6/7] rtc: mpfs: Use devm_pm_set_wake_irq Peng Fan (OSS)
2025-02-05 0:58 ` [PATCH 7/7] rtc: pl031: Use resource managed API to simplify code Peng Fan (OSS)
2025-03-03 8:03 ` [PATCH 0/7] rtc: Use devm_pm_set_wake_irq " Peng Fan
2025-03-03 21:53 ` Alexandre Belloni [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=174103876909.1106916.958645902819103595.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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
all inboxes | Powered by JetHome®