From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: linux@treblig.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reboot: Remove unused unregister_platform_power_off
Date: Sun, 8 Jun 2025 23:03:06 +0300 [thread overview]
Message-ID: <582f86fb-bcf1-4b58-ad54-acacf4326dd1@collabora.com> (raw)
In-Reply-To: <20250608174235.116424-1-linux@treblig.org>
Hi,
On 6/8/25 20:42, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> unregister_platform_power_off() was added as part of 2022's
> commit fb61375ecfba ("kernel/reboot: Add register_platform_power_off()")
> but has remained unused.
>
> Remove it.
>
> Note it's a pair with register_platform_power_off() so
> seems symmetric; however, I think platforms are chosen
> and then stay that way for the boot - so don't
> get unregistered.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
> include/linux/reboot.h | 1 -
> kernel/reboot.c | 16 ----------------
> 2 files changed, 17 deletions(-)
The patches converting those platform drivers to use
register[un]_platform_power_off() haven't been sent to ML. This is the
reason this func is unused.
There were apm_32 [1], platform/iris [2], mcu_mpc8349emitx [3],
olpc-xo1-pm [4] and sgy_cts1000 [5] drivers that I had patches prepared
to convert them to new power-off API. They weren't sent out back then in
2022 because of a nontrivial dependencies between drivers. At least some
of those deps has been resolved by now and potentially the API
conversion may continue. Currently other things keep me busy and don't
have immediate plans to continue the conversion work, maybe sometime later.
Leaving it up to Rafael to decide whether to keep this func unused or
re-add later, once it actually will become needed.
[1]
https://gitlab.collabora.com/dmitry.osipenko/linux-kernel-rd/-/commit/e42f1264161085f01fed16986a23592519d9f49e
[2]
https://gitlab.collabora.com/dmitry.osipenko/linux-kernel-rd/-/commit/24cd048ad801aab6221f2b0bb4576dfc2fe25faa
[3]
https://gitlab.collabora.com/dmitry.osipenko/linux-kernel-rd/-/commit/486b69b43c47d85a0f292dca127f0b9063443a54
[4]
https://gitlab.collabora.com/dmitry.osipenko/linux-kernel-rd/-/commit/fe5344b3f8a8e1c52e1cd7108aa7e615123be4b2
[5]
https://gitlab.collabora.com/dmitry.osipenko/linux-kernel-rd/-/commit/0d761d6139c9dacbbda9f2e095577b084685603f
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-06-08 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 17:42 linux
2025-06-08 20:03 ` Dmitry Osipenko [this message]
2025-06-09 12:24 ` Dr. David Alan Gilbert
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=582f86fb-bcf1-4b58-ad54-acacf4326dd1@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.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 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®