From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: vexpress: move spc driver back under mach-vexpress
Date: Tue, 06 Aug 2013 13:28:12 +0100 [thread overview]
Message-ID: <1375792092.12043.56.camel@hornet> (raw)
In-Reply-To: <20130806085549.GA18810@e102568-lin.cambridge.arm.com>
On Tue, 2013-08-06 at 09:55 +0100, Lorenzo Pieralisi wrote:
> I just wanted to say that sending a patch to fix the issue was inappropriate
> because it depended on where the spc.h has to be created and did not
> know if Pawel was ok with the idea of moving spc back to mach-vexpress.
>
> I am ok with your changes, thank you very much.
Although it works against the goal of removing arch/arm/mach-vexpress
completely ;-) I appreciate the fact that there's more than that on the
way, so yeah, it's fine with me.
Cheers!
Pawel
PS. Apologies about the delay and thanks for testing it out, Lorenzo!
next prev parent reply other threads:[~2013-08-06 12:28 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 [this message]
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
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=1375792092.12043.56.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 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).