From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/05] ARM: shmobile: Use CPU notifiers for SCU boot vector code
Date: Wed, 18 Sep 2013 00:34:54 +0000 [thread overview]
Message-ID: <20130918003453.GA4330@verge.net.au> (raw)
In-Reply-To: <20130914134616.19258.27110.sendpatchset@w520>
On Sat, Sep 14, 2013 at 10:46:16PM +0900, Magnus Damm wrote:
> ARM: shmobile: Use CPU notifiers for SCU boot vector code
>
> [PATCH 01/05] ARM: shmobile: Add CPU notifier based SCU boot vector code
> [PATCH 02/05] ARM: shmobile: Let sh73a0 rely on SCU CPU notifier
> [PATCH 03/05] ARM: shmobile: Let EMEV2 rely on SCU CPU notifier
> [PATCH 04/05] ARM: shmobile: Let r8a7779 rely on SCU CPU notifier
> [PATCH 05/05] ARM: shmobile: Remove shmobile_smp_scu_boot_secondary()
>
> This series converts mach-shmobile to use CPU notifiers for boot vector
> setup for SCU based SoCs such as sh73a0, EMEV2 and r8a7779. This
> allows us to remove the shmobile_smp_scu_boot_secondary() function,
> and it is also ground work for the CPUIdle resume path.
Thanks Magnus, I have queued these up for v3.12.
prev parent reply other threads:[~2013-09-18 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 13:46 [PATCH 00/05] ARM: shmobile: Use CPU notifiers for SCU boot vector code Magnus Damm
2013-09-14 13:46 ` [PATCH 01/05] ARM: shmobile: Add CPU notifier based " Magnus Damm
2013-09-14 13:46 ` [PATCH 02/05] ARM: shmobile: Let sh73a0 rely on SCU CPU notifier Magnus Damm
2013-09-14 13:46 ` [PATCH 03/05] ARM: shmobile: Let EMEV2 " Magnus Damm
2013-09-14 13:46 ` [PATCH 04/05] ARM: shmobile: Let r8a7779 " Magnus Damm
2013-09-14 13:47 ` [PATCH 05/05] ARM: shmobile: Remove shmobile_smp_scu_boot_secondary() Magnus Damm
2013-09-18 0:34 ` Simon Horman [this message]
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=20130918003453.GA4330@verge.net.au \
--to=horms@verge.net.au \
--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).