From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <paulmck@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 09/11] kernel/cpu.c: remove new instance of __cpuinit that crept back in
Date: Tue, 28 Apr 2015 10:24:24 -0400 [thread overview]
Message-ID: <553F9818.8020100@windriver.com> (raw)
In-Reply-To: <20150428131216.GC5553@linux.vnet.ibm.com>
On 15-04-28 09:12 AM, Paul E. McKenney wrote:
> On Mon, Apr 27, 2015 at 06:47:58PM -0400, Paul Gortmaker wrote:
>> We removed __cpuinit support (leaving no-op stubs) quite some time ago.
>> However a new instance was added in commit 00df35f991914db6b8bde8cf0980
>> ("cpu: Defer smpboot kthread unparking until CPU known to scheduler")
>>
>> Since we want to clobber the stubs soon, get this removed now.
>>
>> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> Good catch, queued for 4.2. Please let me know if you need it sooner.
No rush ; no need to queue it either, since I have to keep the
patch in this series in order to be able to remove the stubs in
the 11/11, since I don't want to guess what merge order will
happen in ~6 weeks.
Thanks,
Paul.
--
>
> Thanx, Paul
>
>> ---
>> kernel/cpu.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/cpu.c b/kernel/cpu.c
>> index 94bbe4695232..b4e940d89087 100644
>> --- a/kernel/cpu.c
>> +++ b/kernel/cpu.c
>> @@ -479,7 +479,7 @@ static struct notifier_block smpboot_thread_notifier = {
>> .priority = CPU_PRI_SMPBOOT,
>> };
>>
>> -void __cpuinit smpboot_thread_init(void)
>> +void smpboot_thread_init(void)
>> {
>> register_cpu_notifier(&smpboot_thread_notifier);
>> }
>> --
>> 2.2.1
>>
>
next prev parent reply other threads:[~2015-04-28 14:25 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 ` [PATCH 01/11] sched/core: remove __cpuinit section tag that crept back in Paul Gortmaker
2015-05-08 13:19 ` [tip:sched/core] sched/core: Remove " 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 [this message]
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=553F9818.8020100@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).