From: Krzysztof Kozlowski <krzk@kernel.org>
To: Triet Hoang <triet.hoang.dev@gmail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Michal Simek <michal.simek@amd.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] memory: Convert drivers to DEFINE_SIMPLE_DEV_PM_OPS()
Date: Tue, 25 Aug 2026 11:13:22 +0200 [thread overview]
Message-ID: <d4a0f9f0-6cea-4dac-a315-638376c12e71@kernel.org> (raw)
In-Reply-To: <20260825091118.271720-1-triet.hoang.dev@gmail.com>
On 25/08/2026 11:11, Triet Hoang wrote:
> This series converts the Atmel EBI and PL353 SMC memory drivers to use
> DEFINE_SIMPLE_DEV_PM_OPS().
>
> This is a straightforward cleanup with no functional change intended.
>
> Signed-off-by: Triet Hoang <triet.hoang.dev@gmail.com>
> ---
> Changes in v2:
> - Wrap to 75 ish chars for commit messages.
> - Organize patches into a series with a cover letter.
Did you receive review?
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state in the patch changelog
or cover letter why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-25 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 9:11 [PATCH v2 0/2] memory: Convert drivers to DEFINE_SIMPLE_DEV_PM_OPS() Triet Hoang
2026-08-25 9:11 ` [PATCH v2 1/2] memory: atmel-ebi: Convert " Triet Hoang
2026-08-25 9:11 ` [PATCH v2 2/2] memory: pl353: " Triet Hoang
2026-08-25 9:13 ` Krzysztof Kozlowski [this message]
2026-08-25 9:21 ` [PATCH v2 0/2] memory: Convert drivers " Triet Hoang
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=d4a0f9f0-6cea-4dac-a315-638376c12e71@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=triet.hoang.dev@gmail.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