public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Delete new __cpuinit users and then delete stubs
Date: Tue, 30 Jun 2015 03:28:24 -0400	[thread overview]
Message-ID: <20150630072824.GC8349@windriver.com> (raw)

We removed the __cpuinit stuff in 3.11-rc1 with commit 
22f0a27367742f65130c0fb25ef00f7297e032c1 ("init.h: remove __cpuinit
sections from the kernel") but we left some no-op stubs as
a courtesy to unmerged code.

Here we get rid of the stubs as well, since (as can be seen in these
changes) they are enabling use cases to sneak back in, primarily from
older BSP code that has been living out of tree for some time prior
to getting mainlined.  So we get rid of these "new" users 1st and
then get rid of the stubs.

Obviously, getting rid of the stubs can't happen until all the users
are gone, so I had to keep this together as a series, even though some
of these commits since got picked up into maintainers trees as well.

The nature of this change is such that it should have zero impact on
the generated runtime.

This is one of several independent cleanup branches aimed at
enabling better organization in the init.h and module.h code.  They
have been getting coverage in the linux-next tree for the last month,
in addition to my local testing, which also covers approximately a
half dozen or more architectures.

Original posting:
  "Delete new __cpuinit users and then delete stubs"
  https://lkml.kernel.org/r/1430174880-27958-1-git-send-email-paul.gortmaker@windriver.com

Thanks,
Paul.
---

The following changes since commit 0f57d86787d8b1076ea8f9cbdddda2a46d534a27:

  Linux 4.1-rc8 (2015-06-14 15:51:10 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git tags/cpuinit-v4.1-rc8

for you to fetch changes up to 22c1587adfed1977d26a57ac2831d03e37f8f805:

  init: delete the __cpuinit related stubs (2015-06-16 14:12:23 -0400)

----------------------------------------------------------------
Remove __cpuinit macros and users.

----------------------------------------------------------------
Paul Gortmaker (11):
      arm/mach-keystone: remove legacy __cpuinit sections that crept in
      arm/mach-mvebu: remove legacy __cpuinit sections that crept in
      arm/mach-rockchip: remove legacy __cpuinit section that crept in
      arm/mach-hisi: remove legacy __CPUINIT section that crept in
      mips/ath25: remove legacy __cpuinit section that crept in
      mips/bcm77xx: remove legacy __cpuinit sections that crept in
      mips/c-r4k: remove legacy __cpuinit section that crept in
      mips/mm/tlbex: remove new instance of __cpuinit that crept back in
      sched/core: remove __cpuinit section tag that crept back in.
      kernel/cpu.c: remove new instance of __cpuinit that crept back in
      init: delete the __cpuinit related stubs

 arch/arm/mach-hisi/headsmp.S       |  3 ---
 arch/arm/mach-keystone/platsmp.c   |  4 ++--
 arch/arm/mach-mvebu/headsmp-a9.S   |  3 ---
 arch/arm/mach-mvebu/platsmp-a9.c   |  2 +-
 arch/arm/mach-rockchip/platsmp.c   |  3 +--
 arch/mips/ath25/board.c            |  2 +-
 arch/mips/bcm47xx/prom.c           |  2 +-
 arch/mips/include/asm/pgtable-32.h |  2 +-
 arch/mips/mm/c-r4k.c               |  2 +-
 arch/mips/mm/tlb-r4k.c             |  2 +-
 arch/mips/mm/tlbex.c               |  2 +-
 include/linux/init.h               | 11 -----------
 kernel/cpu.c                       |  2 +-
 kernel/sched/core.c                |  2 +-
 scripts/tags.sh                    |  2 +-
 15 files changed, 13 insertions(+), 31 deletions(-)

                 reply	other threads:[~2015-06-30  7:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150630072824.GC8349@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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