From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
geert+renesas@glider.be
Subject: Re: [PATCH net-next 1/2] can: rcar_can: Convert to DEFINE_SIMPLE_DEV_PM_OPS()
Date: Tue, 15 Jul 2025 00:40:16 +0000 [thread overview]
Message-ID: <175254001601.4040142.14122920462867541735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711101706.2822687-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Fri, 11 Jul 2025 12:15:08 +0200 you wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Convert the Renesas R-Car CAN driver from SIMPLE_DEV_PM_OPS() to
> DEFINE_SIMPLE_DEV_PM_OPS() and pm_sleep_ptr(). This lets us drop the
> __maybe_unused annotations from its suspend and resume callbacks, and
> reduces kernel size in case CONFIG_PM or CONFIG_PM_SLEEP is disabled.
>
> [...]
Here is the summary with links:
- [net-next,1/2] can: rcar_can: Convert to DEFINE_SIMPLE_DEV_PM_OPS()
https://git.kernel.org/netdev/net-next/c/25883e286e7a
- [net-next,2/2] can: rcar_canfd: Drop unused macros
https://git.kernel.org/netdev/net-next/c/0e6639c8505d
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:[~2025-07-15 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 10:15 [PATCH net-next 0/2] pull-request: can-next 2025-07-11 Marc Kleine-Budde
2025-07-11 10:15 ` [PATCH net-next 1/2] can: rcar_can: Convert to DEFINE_SIMPLE_DEV_PM_OPS() Marc Kleine-Budde
2025-07-15 0:40 ` patchwork-bot+netdevbpf [this message]
2025-07-11 10:15 ` [PATCH net-next 2/2] can: rcar_canfd: Drop unused macros Marc Kleine-Budde
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=175254001601.4040142.14122920462867541735.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.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.