From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: LSK merge linux-stable review
Date: Tue, 14 Jan 2014 08:32:06 +0800 [thread overview]
Message-ID: <52D48586.5030801@linaro.org> (raw)
In-Reply-To: <20140113155525.GG11805@arm.com>
On 01/13/2014 11:55 PM, Catalin Marinas wrote:
> On Sat, Jan 11, 2014 at 01:35:52AM +0000, Alex Shi wrote:
>>
>>>>
>>>> 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)
>>
>> Give you the part of modified smp.c file here :)
>
> As I said, you may want to cherry pick 7ade67b5984d0a. It comes in handy
> with GICv3 support (if you later plan to back-port it to this version of
> LSK).
>
Sorry for not make it clear.
We had picked up 7ade67b5984d0a as I showed the contents of function
secondary_start_kernel().
--
Thanks
Alex
next prev parent reply other threads:[~2014-01-14 0: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
2014-01-11 1:35 ` Alex Shi
2014-01-13 15:55 ` Catalin Marinas
2014-01-14 0:32 ` Alex Shi [this message]
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=52D48586.5030801@linaro.org \
--to=alex.shi@linaro.org \
--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).