From: Pawel Moll <pawel.moll@arm.com>
To: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Olof Johansson <olof@lixom.net>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
Jon Medhurst <tixy@linaro.org>, Achin Gupta <Achin.Gupta@arm.com>,
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Subject: Re: [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support
Date: Wed, 17 Jul 2013 10:18:25 +0100 [thread overview]
Message-ID: <1374052705.3146.86.camel@hornet> (raw)
In-Reply-To: <1373990743-23106-1-git-send-email-lorenzo.pieralisi@arm.com>
On Tue, 2013-07-16 at 17:05 +0100, Lorenzo Pieralisi wrote:
> /drivers/mfd is probably not the right place for this code as it stands (but
> probably will be when the entire driver, with DVFS and config interface, is
> complete).
Not that it really matters now, but my vexpress-sysreg rework will -
most likely - leave only skeleton in the MFD (registering mfd_cells) and
other stuff is going to be spread all around. Then I'm planning to move
the remaining of the vexpress-specific initialization to
drivers/platform/arm/vexpress.c, so maybe sticking vexpress-spc.c to
this (non-existing yet) directory would be the right thing to do?
Other than that:
Acked-by: Pawel Moll <pawel.moll@arm.com>
Thanks!
Paweł
next prev parent reply other threads:[~2013-07-17 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:05 [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support Lorenzo Pieralisi
2013-07-17 9:18 ` Pawel Moll [this message]
2013-07-17 10:44 ` Lorenzo Pieralisi
2013-07-17 12:33 ` Nicolas Pitre
2013-07-17 13:29 ` Pawel Moll
2013-07-17 14:16 ` Nicolas Pitre
2013-07-17 14:20 ` Pawel Moll
2013-07-17 15:57 ` Nicolas Pitre
[not found] ` <alpine.LFD.2.03.1307171148160.14924-hIgblCxmbi8OMTOF05IoTw@public.gmane.org>
2013-07-17 17:00 ` Russell King - ARM Linux
2013-07-17 18:29 ` Nicolas Pitre
2013-07-17 21:23 ` Samuel Ortiz
2013-07-17 22:22 ` Nicolas Pitre
2013-07-17 22:47 ` Samuel Ortiz
2013-07-17 21:10 ` Samuel Ortiz
[not found] ` <1373990743-23106-1-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2013-07-16 16:05 ` [RFC PATCH v5 1/1] drivers: mfd: vexpress: add Serial Power Controller (SPC) support Lorenzo Pieralisi
2013-07-16 20:05 ` Rob Herring
2013-07-16 23:32 ` Nicolas Pitre
2013-07-17 3:26 ` [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support Nicolas Pitre
2013-07-17 21:07 ` Samuel Ortiz
2013-07-18 9:28 ` Lorenzo Pieralisi
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=1374052705.3146.86.camel@hornet \
--to=pawel.moll@arm.com \
--cc=Achin.Gupta@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Sudeep.KarkadaNagesha@arm.com \
--cc=amit.kucheria@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=olof@lixom.net \
--cc=sameo@linux.intel.com \
--cc=tixy@linaro.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).