mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Remove unused code after IA-64 removal
Date: Thu, 16 Nov 2023 14:36:35 +0100	[thread overview]
Message-ID: <20231116133638.1636277-1-hca@linux.ibm.com> (raw)

While looking into something different I noticed that there are a couple of
Kconfig options which were only selected by IA-64 and which are now unused.

So remove them and simplify the code a bit.

Heiko Carstens (3):
  arch: remove ARCH_THREAD_STACK_ALLOCATOR
  arch: remove ARCH_TASK_STRUCT_ALLOCATOR
  arch: remove ARCH_TASK_STRUCT_ON_STACK

 arch/Kconfig                 | 13 -------------
 arch/powerpc/kexec/core_64.c |  3 +--
 include/linux/init_task.h    |  7 -------
 include/linux/sched.h        |  2 --
 init/init_task.c             | 10 ++--------
 kernel/fork.c                | 26 --------------------------
 6 files changed, 3 insertions(+), 58 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-11-16 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 13:36 Heiko Carstens [this message]
2023-11-16 13:36 ` [PATCH 1/3] arch: remove ARCH_THREAD_STACK_ALLOCATOR Heiko Carstens
2023-11-16 13:36 ` [PATCH 2/3] arch: remove ARCH_TASK_STRUCT_ALLOCATOR Heiko Carstens
2023-11-16 13:36 ` [PATCH 3/3] arch: remove ARCH_TASK_STRUCT_ON_STACK Heiko Carstens
2023-11-21 16:24 ` [PATCH 0/3] Remove unused code after IA-64 removal Ard Biesheuvel
2023-11-21 16:38 ` Arnd Bergmann

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=20231116133638.1636277-1-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.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®