public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: paul.gortmaker@windriver•com (Paul Gortmaker)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 02/11] arm/mach-keystone: remove legacy __cpuinit sections that crept in
Date: Wed, 6 May 2015 10:59:01 -0400	[thread overview]
Message-ID: <20150506145901.GB12108@windriver.com> (raw)
In-Reply-To: <20150506103704.GJ2067@n2100.arm.linux.org.uk>

[Re: [PATCH 02/11] arm/mach-keystone: remove legacy __cpuinit sections that crept in] On 06/05/2015 (Wed 11:37) Russell King - ARM Linux wrote:

> On Mon, Apr 27, 2015 at 06:47:51PM -0400, Paul Gortmaker wrote:
> > We removed __cpuinit support (leaving no-op stubs) quite some time
> > ago.  However two crept back in as of commit 5eb3da7246a5b2dfac9f38
> > ("ARM: keystone: Switch over to coherent memory address space")
> > 
> > Since we want to clobber the stubs too, get these removed now.
> > 
> > Cc: Santosh Shilimkar <santosh.shilimkar@ti•com>
> 
> Santosh's email is now: Santosh Shilimkar <ssantosh@kernel•org>

Thanks - will fix locally and ensure that is what goes into linux-next
etc. but won't bother respamming everyone with the whole series for it.

P.
--

> 
> > Cc: linux-arm-kernel at lists.infradead.org
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver•com>
> > ---
> >  arch/arm/mach-keystone/platsmp.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/mach-keystone/platsmp.c b/arch/arm/mach-keystone/platsmp.c
> > index 5f46a7cf907b..7f99550cad46 100644
> > --- a/arch/arm/mach-keystone/platsmp.c
> > +++ b/arch/arm/mach-keystone/platsmp.c
> > @@ -40,14 +40,14 @@ static int keystone_smp_boot_secondary(unsigned int cpu,
> >  }
> >  
> >  #ifdef CONFIG_ARM_LPAE
> > -static void __cpuinit keystone_smp_secondary_initmem(unsigned int cpu)
> > +static void keystone_smp_secondary_initmem(unsigned int cpu)
> >  {
> >  	pgd_t *pgd0 = pgd_offset_k(0);
> >  	cpu_set_ttbr(1, __pa(pgd0) + TTBR1_OFFSET);
> >  	local_flush_tlb_all();
> >  }
> >  #else
> > -static inline void __cpuinit keystone_smp_secondary_initmem(unsigned int cpu)
> > +static inline void keystone_smp_secondary_initmem(unsigned int cpu)
> >  {}
> >  #endif
> >  
> > -- 
> > 2.2.1
> > 
> > 
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 
> -- 
> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
> according to speedtest.net.

  reply	other threads:[~2015-05-06 14:59 UTC|newest]

Thread overview: 10+ 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 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 [this message]
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

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=20150506145901.GB12108@windriver.com \
    --to=paul.gortmaker@windriver$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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