From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: vexpress: TC2 MCPM/SPC cleanups
Date: Tue, 06 Aug 2013 18:32:54 +0100 [thread overview]
Message-ID: <1375810374.12043.104.camel@hornet> (raw)
In-Reply-To: <CAOesGMhQJ65B1FT15Wivm3=n_TvvTDgisq+6MjXHWF6OfQGuTg@mail.gmail.com>
On Tue, 2013-08-06 at 18:25 +0100, Olof Johansson wrote:
> > I dare to disagree. And the reason is simple - arch/arm64. It's vexpress
> > as well, and we'll be in the same position.
>
> Actually, no -- PSCI will be mandatory there so there will be no need
> to have these kernel components.
Oh, SPC must die with TC2, no argument from me here. That's why I don't
really mind it being in arch/arm/mach-vexpress today. If it turns out
that it's the last and only thing there, we can discuss it again.
Pawe?
next prev parent reply other threads:[~2013-08-06 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 4:09 [PATCH 0/3] ARM: vexpress: TC2 MCPM/SPC cleanups Olof Johansson
2013-08-05 4:09 ` [PATCH 1/3] ARM: vexpress: move spc driver back under mach-vexpress Olof Johansson
2013-08-05 9:52 ` Lorenzo Pieralisi
2013-08-05 23:26 ` Olof Johansson
2013-08-06 8:55 ` Lorenzo Pieralisi
2013-08-06 12:28 ` Pawel Moll
2013-08-05 4:09 ` [PATCH 2/3] ARM: vexpress: make spc code TC2-only Olof Johansson
2013-08-05 9:55 ` Lorenzo Pieralisi
2013-08-05 23:28 ` Olof Johansson
2013-08-05 4:09 ` [PATCH 3/3] ARM: vexpress: don't print virtual address in dmesg Olof Johansson
2013-08-05 9:47 ` [PATCH 0/3] ARM: vexpress: TC2 MCPM/SPC cleanups Lorenzo Pieralisi
2013-08-05 16:45 ` Olof Johansson
2013-08-06 16:19 ` Pawel Moll
2013-08-06 16:44 ` Olof Johansson
2013-08-06 17:03 ` Pawel Moll
2013-08-06 17:25 ` Olof Johansson
2013-08-06 17:32 ` Pawel Moll [this message]
2013-08-06 17:08 ` Lorenzo Pieralisi
2013-08-06 16:55 ` Lorenzo Pieralisi
2013-08-06 17:06 ` Pawel Moll
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=1375810374.12043.104.camel@hornet \
--to=pawel.moll@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 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.