From: avorontsov@dev.rtsoft.ru (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] SMP support for CNS3xxx + some SMP SCU cleanups
Date: Tue, 27 Jul 2010 21:11:09 +0400 [thread overview]
Message-ID: <20100727171109.GA7929@oksana.dev.rtsoft.ru> (raw)
Hello Russell,
These patches were posted before, i.e.
1/3 ARM: Factor out secondary CPU bootup code from VExpress platforms
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/018410.html
2/3 ARM: RealView: Switch to generic SCU routines
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/018411.html
3/3 ARM: cns3xxx: Add support for SMP
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/018412.html
In this updated series I split patch 1/3 into two, i.e. now it is:
1/4 ARM: SCU: Add generic routines for secondary CPU bootup
and
3/4 ARM: VExpress: Switch to generic SCU routines
This was done so that new feature addition doesn't depend on a
cleanup patch.
I tested 4/4 on a RealView PBX platform, so it should be pretty
much OK. 3/4 was only compile-tested, but it should be OK as
generic SCU code was mostly copied from VExpress platforms.
In the end, I consider patches 1/4 and 2/4 as 100% safe, so I'd
like them to go into 2.6.36 via your patch tracking system. What
do you think?
Thanks,
--
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2
next reply other threads:[~2010-07-27 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 17:11 Anton Vorontsov [this message]
2010-07-27 17:11 ` [PATCH 1/4] ARM: SCU: Add generic routines for secondary CPU bootup Anton Vorontsov
2010-07-31 15:41 ` Russell King - ARM Linux
2010-07-31 16:38 ` Anton Vorontsov
2010-07-27 17:11 ` [PATCH 2/4] ARM: cns3xxx: Add support for SMP Anton Vorontsov
2010-07-27 17:11 ` [PATCH 3/4] ARM: VExpress: Switch to generic SCU routines Anton Vorontsov
2010-07-27 17:11 ` [PATCH 4/4] ARM: RealView: " Anton Vorontsov
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=20100727171109.GA7929@oksana.dev.rtsoft.ru \
--to=avorontsov@dev.rtsoft.ru \
--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).