From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: LSK merge linux-stable review
Date: Fri, 10 Jan 2014 16:32:39 +0000 [thread overview]
Message-ID: <20140110163239.GF925@arm.com> (raw)
In-Reply-To: <52D01234.5040402@linaro.org>
On Fri, Jan 10, 2014 at 03:31:00PM +0000, Alex Shi wrote:
> On 01/10/2014 06:56 PM, Catalin Marinas wrote:
> > On Fri, Jan 10, 2014 at 02:58:20AM +0000, Alex Shi wrote:
> >> commit 450cdfa9c5713551ab1438ab210679868b52a994
> >> Merge: bf78886 8b4ed85
> >> Author: Alex Shi <alex.shi@linaro.org>
> >> Date: Fri Jan 10 10:50:57 2014 +0800
> >>
> >> Merge remote-tracking branch 'stable/linux-3.10.y' into linux-linaro-lsk
> >>
> >> Conflicts:
> >> arch/arm64/kernel/smp.c
> >>
> >> Signed-off-by: Alex Shi <alex.shi@linaro.org>
> >>
> >> diff --cc arch/arm64/kernel/smp.c
> >> index 5e9d274,9c93e12..87340fd
> >> --- a/arch/arm64/kernel/smp.c
> >> +++ b/arch/arm64/kernel/smp.c
> >> @@@ -150,17 -187,17 +150,10 @@@ asmlinkage void __cpuinit secondary_sta
> >> preempt_disable();
> >> trace_hardirqs_off();
> >>
> >> - /*
> >> - * Let the primary processor know we're out of the
> >> - * pen, then head off into the C entry point
> >> - */
> >> - write_pen_release(INVALID_HWID);
> >> + if (cpu_ops[cpu]->cpu_postboot)
> >> + cpu_ops[cpu]->cpu_postboot();
> >>
> >> -- /*
> >> - * Enable local interrupts.
> >> - */
> >> - notify_cpu_starting(cpu);
> >
> > This kind of diff always confuses me but notify_cpu_starting() should be
> > present in the resulting file. Is it further down?
> >
>
> the first column '-/+' means contents was removed/added from file
> 5e9d274. the 2nd column '-/+' means contents was removed/added from file
> 9c93e12.
>
> Yes, The notify_cpu_starting kept in final file later.
Just make sure it is in line with commit 7ade67b5984d0a (arm64: move
enabling of GIC before CPUs are set online)
--
Catalin
next prev parent reply other threads:[~2014-01-10 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140110013011.GA6447@alex-shi>
[not found] ` <52CF61CC.40305@linaro.org>
2014-01-10 10:56 ` LSK merge linux-stable review Catalin Marinas
2014-01-10 15:31 ` Alex Shi
2014-01-10 16:32 ` Catalin Marinas [this message]
2014-01-11 1:35 ` Alex Shi
2014-01-13 15:55 ` Catalin Marinas
2014-01-14 0:32 ` Alex Shi
2014-01-14 9:45 ` Catalin Marinas
2014-01-14 10:20 ` Alex Shi
[not found] ` <CADRr18M=sNsSD1PtoPeQw+DuQtn=p2uwFOLjEE-ztea3SnFHEQ@mail.gmail.com>
2014-01-10 15:51 ` Alex Shi
2014-01-10 15:53 ` Alex Shi
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=20140110163239.GF925@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.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).