linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <linux-kernel@vger.kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	Corey Minyard <cminyard@mvista.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH 01/11] sched/core: remove __cpuinit section tag that crept back in.
Date: Mon, 27 Apr 2015 18:47:50 -0400	[thread overview]
Message-ID: <1430174880-27958-2-git-send-email-paul.gortmaker@windriver.com> (raw)
In-Reply-To: <1430174880-27958-1-git-send-email-paul.gortmaker@windriver.com>

We removed __cpuinit support (leaving no-op stubs) quite some time
ago.  However this one crept back in as of commit a803f0261bb2bb57aab
("sched: Initialize rq->age_stamp on processor start")

Since we want to clobber the stubs too, get this removed now.

Cc: Corey Minyard <cminyard@mvista.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
 kernel/sched/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index f9123a82cbb6..7709aaa5b2cf 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5330,7 +5330,7 @@ static struct notifier_block migration_notifier = {
 	.priority = CPU_PRI_MIGRATION,
 };
 
-static void __cpuinit set_cpu_rq_start_time(void)
+static void set_cpu_rq_start_time(void)
 {
 	int cpu = smp_processor_id();
 	struct rq *rq = cpu_rq(cpu);
-- 
2.2.1


  reply	other threads:[~2015-04-27 22:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 22:47 [PATCH 00/11] Delete new __cpuinit users and then delete stubs Paul Gortmaker
2015-04-27 22:47 ` Paul Gortmaker [this message]
2015-05-08 13:19   ` [tip:sched/core] sched/core: Remove __cpuinit section tag that crept back in tip-bot for Paul Gortmaker
2015-04-27 22:47 ` [PATCH 02/11] arm/mach-keystone: remove legacy __cpuinit sections that crept in Paul Gortmaker
2015-05-06 10:37   ` Russell King - ARM Linux
2015-05-06 14:59     ` Paul Gortmaker
2015-05-06 17:10     ` santosh shilimkar
2015-05-06 22:57       ` Paul Gortmaker
2015-04-27 22:47 ` [PATCH 03/11] arm/mach-mvebu: " Paul Gortmaker
2015-04-28 16:06   ` Gregory CLEMENT
2015-04-27 22:47 ` [PATCH 04/11] arm/mach-rockchip: remove legacy __cpuinit section " Paul Gortmaker
2015-04-27 22:47 ` [PATCH 05/11] arm/mach-hisi: remove legacy __CPUINIT " Paul Gortmaker
2015-04-27 22:47 ` [PATCH 06/11] mips/ath25: remove legacy __cpuinit " Paul Gortmaker
2015-04-28  9:28   ` Sergey Ryazanov
2015-04-27 22:47 ` [PATCH 07/11] mips/bcm77xx: remove legacy __cpuinit sections " Paul Gortmaker
2015-04-27 22:47 ` [PATCH 08/11] mips/c-r4k: remove legacy __cpuinit section " Paul Gortmaker
2015-04-27 22:47 ` [PATCH 09/11] kernel/cpu.c: remove new instance of __cpuinit that crept back in Paul Gortmaker
2015-04-28 13:12   ` Paul E. McKenney
2015-04-28 14:24     ` Paul Gortmaker
2015-04-27 22:47 ` [PATCH 10/11] mips/mm/tlbex: " Paul Gortmaker
2015-04-27 22:48 ` [PATCH 11/11] init: delete the __cpuinit related stubs Paul Gortmaker

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=1430174880-27958-2-git-send-email-paul.gortmaker@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).