From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] ARM: OMAP2+: SmartReflex: move the platform specific macros in plat-omap
Date: Thu, 15 Mar 2012 10:14:00 -0700 [thread overview]
Message-ID: <20120315171359.GA7276@atomide.com> (raw)
In-Reply-To: <1331829845-9526-3-git-send-email-j-pihet@ti.com>
* jean.pihet at 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.
Regards,
Tony
next prev parent reply other threads:[~2012-03-15 17:14 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 at newoldbits.com
2012-03-15 16:43 ` [PATCH 01/10] ARM: OMAP3+: voltage: export functions to plat/voltage.h jean.pihet at newoldbits.com
2012-03-15 16:43 ` [PATCH 02/10] ARM: OMAP2+: SmartReflex: move the platform specific macros in plat-omap jean.pihet at newoldbits.com
2012-03-15 17:14 ` Tony Lindgren [this message]
2012-03-16 15:19 ` Jean Pihet
2012-04-18 20:18 ` Tony Lindgren
2012-03-15 16:43 ` [PATCH 03/10] ARM: OMAP3+: SmartReflex: class drivers should use struct omap_sr * jean.pihet at newoldbits.com
2012-03-15 16:43 ` [PATCH 04/10] ARM: OMAP2+: smartreflex: Use the names from hwmod data instead of voltage domains jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 05/10] ARM: OMAP3: hwmod: rename the smartreflex entries jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 06/10] ARM: OMAP2+: SmartReflex: use the platform header file for voltage functions jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 07/10] ARM: OMAP2+: SmartReflex: introduce a busy loop condition test macro jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 08/10] ARM: OMAP2+: SmartReflex: Use per-OPP data structure jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 09/10] ARM: OMAP2+: SmartReflex: add POWER_AVS Kconfig options jean.pihet at newoldbits.com
2012-03-15 16:44 ` [PATCH 10/10] ARM: OMAP: SmartReflex: Move smartreflex driver to drivers/ jean.pihet at newoldbits.com
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=20120315171359.GA7276@atomide.com \
--to=tony@atomide.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).