From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: vexpress: move spc driver back under mach-vexpress
Date: Mon, 5 Aug 2013 16:26:05 -0700 [thread overview]
Message-ID: <20130805232605.GA32172@quad.lixom.net> (raw)
In-Reply-To: <20130805095235.GB29090@e102568-lin.cambridge.arm.com>
On Mon, Aug 05, 2013 at 10:52:35AM +0100, Lorenzo Pieralisi wrote:
> > +#include "spc.h"
>
> Missing. Should we add it to mach-vexpress/include/mach ?
Oops, missed the git add on it.
No, include/mach is going away on all multiplatform platforms. Since the
exposed functions are only used in the other file in the same directory, local
include file is the way to go.
> I have not sent a patch to check what we should do first and if Pawel is
> ok with these changes.
Not sure I'm following, but see above.
-Olof
next prev parent reply other threads:[~2013-08-05 23:26 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 [this message]
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
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=20130805232605.GA32172@quad.lixom.net \
--to=olof@lixom.net \
--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.