From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <linux@armlinux.org.uk>, <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:52:07 +0800 [thread overview]
Message-ID: <1309c436-4e7f-89a3-3b33-abddaaac410c@huawei.com> (raw)
In-Reply-To: <20240702075742.945768-1-ruanjinjie@huawei.com>
Gentle ping.
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(-)
>
next prev parent reply other threads:[~2024-07-31 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 7:57 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 ` Jinjie Ruan [this message]
2024-07-31 8:27 ` [PATCH RESEND 0/2] ARM: Switch over to GENERIC_CPU_DEVICES Russell King (Oracle)
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=1309c436-4e7f-89a3-3b33-abddaaac410c@huawei.com \
--to=ruanjinjie@huawei.com \
--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=linux@armlinux.org.uk \
--cc=robh@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 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®