From: Tony Lindgren <tony@atomide.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 02/10] ARM: OMAP2+: SmartReflex: move the platform specific macros in plat-omap
Date: Wed, 18 Apr 2012 13:18:07 -0700 [thread overview]
Message-ID: <20120418201807.GQ21106@atomide.com> (raw)
In-Reply-To: <CAORVsuUp9VBX1XbkQkcq91XsbRSut1RC6KCNPFHrX+RfWv7hQA@mail.gmail.com>
* Jean Pihet <jean.pihet@newoldbits.com> [120316 08:22]:
> Hi Tony,
>
> On Thu, Mar 15, 2012 at 6:14 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * jean.pihet@newoldbits.com <jean.pihet@newoldbits.com> [120315 09:47]:
> >> From: Jean Pihet <j-pihet@ti.com>
> >>
> >> Move the platform specific macros from the smartreflex header file
> >> (arch/arm/mach-omap2/smartreflex.h) in a new header file in plat-omap
> >> (arch/arm/plat-omap/include/plat/smartreflex.h).
> >>
> >> This change makes the SmartReflex implementation ready for the move
> >> to drivers/.
> >
> > Glad to see this happening!
> >
> > This would be better located in linux/power/smartreflex.h rather than
> > plat/smartreflex.h.
> Ok. Is the file name still Ok in that case? Should it mention OMAP?
Well I guess smartreflex is enough, in theory it could be on other
processors than omap too.
Tony
next prev parent reply other threads:[~2012-04-18 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 16:43 [PATCH 00/10] PM: Create the AVS class of drivers jean.pihet
2012-03-15 16:43 ` [PATCH 01/10] ARM: OMAP3+: voltage: export functions to plat/voltage.h jean.pihet
2012-03-15 16:43 ` [PATCH 02/10] ARM: OMAP2+: SmartReflex: move the platform specific macros in plat-omap jean.pihet
2012-03-15 17:14 ` Tony Lindgren
2012-03-16 15:19 ` Jean Pihet
2012-04-18 20:18 ` Tony Lindgren [this message]
2012-03-15 16:43 ` [PATCH 03/10] ARM: OMAP3+: SmartReflex: class drivers should use struct omap_sr * jean.pihet
2012-03-15 16:43 ` [PATCH 04/10] ARM: OMAP2+: smartreflex: Use the names from hwmod data instead of voltage domains jean.pihet
2012-03-15 16:44 ` [PATCH 05/10] ARM: OMAP3: hwmod: rename the smartreflex entries jean.pihet
2012-03-15 16:44 ` [PATCH 06/10] ARM: OMAP2+: SmartReflex: use the platform header file for voltage functions jean.pihet
2012-03-15 16:44 ` [PATCH 07/10] ARM: OMAP2+: SmartReflex: introduce a busy loop condition test macro jean.pihet
2012-03-15 16:44 ` [PATCH 08/10] ARM: OMAP2+: SmartReflex: Use per-OPP data structure jean.pihet
2012-03-15 16:44 ` [PATCH 09/10] ARM: OMAP2+: SmartReflex: add POWER_AVS Kconfig options jean.pihet
2012-03-15 16:44 ` [PATCH 10/10] ARM: OMAP: SmartReflex: Move smartreflex driver to drivers/ jean.pihet
2012-03-15 21:19 ` Rafael J. Wysocki
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=20120418201807.GQ21106@atomide.com \
--to=tony@atomide.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).