From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: arnd@arndb.de, afd@ti.com, akpm@linux-foundation.org,
linus.walleij@linaro.org, eric.devolder@oracle.com,
ardb@kernel.org, gregkh@linuxfoundation.org, deller@gmx.de,
javierm@redhat.com, bhe@redhat.com, robh@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND 0/2] ARM: Switch over to GENERIC_CPU_DEVICES
Date: Wed, 31 Jul 2024 09:27:49 +0100 [thread overview]
Message-ID: <Zqn1hVHUdsDjhtT8@shell.armlinux.org.uk> (raw)
In-Reply-To: <1309c436-4e7f-89a3-3b33-abddaaac410c@huawei.com>
On Wed, Jul 31, 2024 at 09:52:07AM +0800, Jinjie Ruan wrote:
> On 2024/7/2 15:57, Jinjie Ruan wrote:
> > Currently, almost all architectures have switched to GENERIC_CPU_DEVICES,
> > except for arm32. Also switch over to GENERIC_CPU_DEVICES, which can also
> > make the code more concise.
> >
> > Jinjie Ruan (2):
> > ARM: Switch over to GENERIC_CPU_DEVICES using arch_register_cpu()
> > ARM: Convert to arch_cpu_is_hotpluggable()
> >
> > arch/arm/Kconfig | 1 +
> > arch/arm/include/asm/cpu.h | 1 -
> > arch/arm/kernel/setup.c | 14 ++------------
> > 3 files changed, 3 insertions(+), 13 deletions(-)
I think it's fine, but it needs to end up in the patch system to be
applied. Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-07-31 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 7:57 [PATCH RESEND 0/2] ARM: Switch over to GENERIC_CPU_DEVICES Jinjie Ruan
2024-07-02 7:57 ` [PATCH RESEND 1/2] ARM: Switch over to GENERIC_CPU_DEVICES using arch_register_cpu() Jinjie Ruan
2024-07-02 7:57 ` [PATCH RESEND 2/2] ARM: Convert to arch_cpu_is_hotpluggable() Jinjie Ruan
2024-07-31 1:52 ` [PATCH RESEND 0/2] ARM: Switch over to GENERIC_CPU_DEVICES Jinjie Ruan
2024-07-31 8:27 ` Russell King (Oracle) [this message]
2024-07-31 8:57 ` Jinjie Ruan
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=Zqn1hVHUdsDjhtT8@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=deller@gmx.de \
--cc=eric.devolder@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.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 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.