From: Paul Mundt <lethal@linux-sh.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/03] ARM: mach-shmobile: Initial SMP support
Date: Fri, 07 Jan 2011 01:51:39 +0000 [thread overview]
Message-ID: <20110107015139.GE22477@linux-sh.org> (raw)
In-Reply-To: <20101214095703.GG14606@linux-sh.org>
On Tue, Dec 14, 2010 at 06:57:03PM +0900, Paul Mundt wrote:
> On Tue, Dec 14, 2010 at 04:56:47PM +0900, Magnus Damm wrote:
> > ARM: mach-shmobile: Initial SMP support
> >
> > [PATCH 01/03] ARM: mach-shmobile: SMP base support
> > [PATCH 02/03] ARM: mach-shmobile: Enable SMP support
> > [PATCH 03/03] ARM: mach-shmobile: sh73a0 SMP support
> >
> > These patches add SMP framework support for R-Mobile and
> > SH-Mobile processors, together with hardware specific SMP
> > support for the sh73a0 processor.
> >
> > Survives onlining and offlining of secondary processor cores
> > through sysfs. Should compile and boot regardless of
> > CONFIG_SMP, CONFIG_HOTPLUG_CPU and CONFIG_LOCAL_TIMERS.
> >
> > I suggest that patch 1 and 3 are taken through sh-2.6 and
> > patch 2 goes through the RMK patch tracker.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Applied to rmobile/smp, thanks.
>
> There are integration issues with regards to the GIC changes that I'll
> have to take care of during the merge window regardless, so resolving the
> CONFIG_SMP thing at that point should be pretty straightforward. My plan
> is to wait until after Russell merges, merge your stuff on top of that,
> and then send the updated bits to Linus in one shot.
>
> In order to avoid clashes with -next for now however I won't be merging
> the topic branch in to my -latest branch. Given that the number of boards
> in the wild for this at the moment are in the single digits, I'm not too
> worried about the amount of time these changes spend in -next so long as
> no regressions are introduced for the other boards.
I've now merged the rmobile/smp branch in to rmobile-latest, which
resolves the minor clashes with Russell's merge as well as the
entry-macro rework.
WARNING: multiple messages have this Message-ID (diff)
From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/03] ARM: mach-shmobile: Initial SMP support
Date: Fri, 7 Jan 2011 10:51:39 +0900 [thread overview]
Message-ID: <20110107015139.GE22477@linux-sh.org> (raw)
In-Reply-To: <20101214095703.GG14606@linux-sh.org>
On Tue, Dec 14, 2010 at 06:57:03PM +0900, Paul Mundt wrote:
> On Tue, Dec 14, 2010 at 04:56:47PM +0900, Magnus Damm wrote:
> > ARM: mach-shmobile: Initial SMP support
> >
> > [PATCH 01/03] ARM: mach-shmobile: SMP base support
> > [PATCH 02/03] ARM: mach-shmobile: Enable SMP support
> > [PATCH 03/03] ARM: mach-shmobile: sh73a0 SMP support
> >
> > These patches add SMP framework support for R-Mobile and
> > SH-Mobile processors, together with hardware specific SMP
> > support for the sh73a0 processor.
> >
> > Survives onlining and offlining of secondary processor cores
> > through sysfs. Should compile and boot regardless of
> > CONFIG_SMP, CONFIG_HOTPLUG_CPU and CONFIG_LOCAL_TIMERS.
> >
> > I suggest that patch 1 and 3 are taken through sh-2.6 and
> > patch 2 goes through the RMK patch tracker.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Applied to rmobile/smp, thanks.
>
> There are integration issues with regards to the GIC changes that I'll
> have to take care of during the merge window regardless, so resolving the
> CONFIG_SMP thing at that point should be pretty straightforward. My plan
> is to wait until after Russell merges, merge your stuff on top of that,
> and then send the updated bits to Linus in one shot.
>
> In order to avoid clashes with -next for now however I won't be merging
> the topic branch in to my -latest branch. Given that the number of boards
> in the wild for this at the moment are in the single digits, I'm not too
> worried about the amount of time these changes spend in -next so long as
> no regressions are introduced for the other boards.
I've now merged the rmobile/smp branch in to rmobile-latest, which
resolves the minor clashes with Russell's merge as well as the
entry-macro rework.
next prev parent reply other threads:[~2011-01-07 1:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 7:56 [PATCH 00/03] ARM: mach-shmobile: Initial SMP support Magnus Damm
2010-12-14 7:56 ` Magnus Damm
2010-12-14 7:56 ` [PATCH 01/03] ARM: mach-shmobile: SMP base support Magnus Damm
2010-12-14 7:56 ` Magnus Damm
2010-12-17 8:42 ` Russell King - ARM Linux
2010-12-17 8:42 ` Russell King - ARM Linux
2010-12-17 11:39 ` Magnus Damm
2010-12-17 11:39 ` Magnus Damm
2010-12-14 7:57 ` [PATCH 02/03] ARM: mach-shmobile: Enable SMP support Magnus Damm
2010-12-14 7:57 ` Magnus Damm
2010-12-14 7:57 ` [PATCH 03/03] ARM: mach-shmobile: sh73a0 " Magnus Damm
2010-12-14 7:57 ` Magnus Damm
2010-12-14 9:57 ` [PATCH 00/03] ARM: mach-shmobile: Initial " Paul Mundt
2010-12-14 9:57 ` Paul Mundt
2011-01-07 1:51 ` Paul Mundt [this message]
2011-01-07 1:51 ` Paul Mundt
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=20110107015139.GE22477@linux-sh.org \
--to=lethal@linux-sh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.