From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] vmlinux.lds.h: remove unused CPU_KEEP and CPU_DISCARD macros
Date: Sun, 1 Oct 2023 01:34:22 -0400 [thread overview]
Message-ID: <ZRkE3q0Z9psMYVqi@windriver.com> (raw)
In-Reply-To: <20230930071335.1224500-1-masahiroy@kernel.org>
[[PATCH] vmlinux.lds.h: remove unused CPU_KEEP and CPU_DISCARD macros] On 30/09/2023 (Sat 16:13) Masahiro Yamada wrote:
> Remove the left-over of commit e24f6628811e ("modpost: remove all
> traces of cpuinit/cpuexit sections").
Hard to believe that cpuinit/cpuexit removal was over 10 years ago now.
Acked-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Thanks,
Paul.
--
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> include/asm-generic/vmlinux.lds.h | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index 9c59409104f6..67d8dd2f1bde 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -138,13 +138,6 @@
> * are handled as text/data or they can be discarded (which
> * often happens at runtime)
> */
> -#ifdef CONFIG_HOTPLUG_CPU
> -#define CPU_KEEP(sec) *(.cpu##sec)
> -#define CPU_DISCARD(sec)
> -#else
> -#define CPU_KEEP(sec)
> -#define CPU_DISCARD(sec) *(.cpu##sec)
> -#endif
>
> #if defined(CONFIG_MEMORY_HOTPLUG)
> #define MEM_KEEP(sec) *(.mem##sec)
> --
> 2.39.2
>
prev parent reply other threads:[~2023-10-01 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 7:13 [PATCH] vmlinux.lds.h: remove unused CPU_KEEP and CPU_DISCARD macros Masahiro Yamada
2023-10-01 5:34 ` Paul Gortmaker [this message]
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=ZRkE3q0Z9psMYVqi@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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.