From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/19] ARM: OMAP3+: SmartReflex: bugfixes
Date: Tue, 31 Jan 2012 09:08:30 -0800 [thread overview]
Message-ID: <20120131170830.GJ9339@atomide.com> (raw)
In-Reply-To: <1328003912-11709-1-git-send-email-j-pihet@ti.com>
* Jean Pihet <jean.pihet@newoldbits.com> [120131 01:28]:
> Integrate the latest SmartReflex bufixes from Felipe Balbi [1] and
> Nishant Menon [2], plus misc bugfixes.
We should move this to live under drivers somewhere. So
I'd like to see just minimal cleanup in the current location,
then move it to drivers before further patching.
Is this the minimal cleanup needed before doing that, or
what's your plan regarding moving it to drivers?
Cheers,
Tony
next prev parent reply other threads:[~2012-01-31 17:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 9:58 [PATCH v2 00/19] ARM: OMAP3+: SmartReflex: bugfixes Jean Pihet
2012-01-31 9:58 ` [PATCH 01/19] ARM: OMAP3+: SmartReflex: Layer Cleanup [V4] Jean Pihet
2012-01-31 9:58 ` [PATCH 02/19] ARM: OMAP3+: SmartReflex: add missing error-handling code Jean Pihet
2012-01-31 9:58 ` [PATCH 03/19] ARM: OMAP3+: SmartReflex: fix err interrupt disable sequence Jean Pihet
2012-01-31 9:58 ` [PATCH 04/19] ARM: OMAP3+: SmartReflex Class3: disable errorgen before disable VP Jean Pihet
2012-01-31 9:58 ` [PATCH 05/19] ARM: OMAP3+: SmartReflex: Add a shutdown hook Jean Pihet
2012-01-31 9:58 ` [PATCH 06/19] ARM: OMAP3+: SmartReflex: Fix status masking in ERRCONFIG register Jean Pihet
2012-01-31 9:58 ` [PATCH 07/19] ARM: OMAP3+: SmartReflex: clear ERRCONFIG_VPBOUNDINTST only on a need Jean Pihet
2012-01-31 9:58 ` [PATCH 08/19] ARM: OMAP3+: hwmod: add SmartReflex IRQs Jean Pihet
2012-01-31 9:58 ` [PATCH 09/19] ARM: OMAP3+: SmartReflex: introduce class init, deinit and priv data Jean Pihet
2012-01-31 9:58 ` [PATCH 10/19] ARM: OMAP3+: SmartReflex: introduce notifiers flags Jean Pihet
2012-01-31 9:58 ` [PATCH 11/19] ARM: OMAP3+: SmartReflex: introduce notifier_control Jean Pihet
2012-01-31 9:58 ` [PATCH 12/19] ARM: OMAP3+: SmartReflex: disable spamming interrupts Jean Pihet
2012-01-31 9:58 ` [PATCH 13/19] ARM: OMAP3+: SmartReflex: introduce class private data per voltage domain Jean Pihet
2012-01-31 9:58 ` [PATCH 14/19] ARM: OMAP3+: SmartReflex Class3: restrict CPU to run on Jean Pihet
2012-01-31 9:58 ` [PATCH 15/19] ARM: OMAP3+: SmartReflex: add missing platform_set_drvdata() Jean Pihet
2012-01-31 9:58 ` [PATCH 16/19] ARM: OMAP3+: SmartReflex: move late_initcall() closer to its argument Jean Pihet
2012-01-31 9:58 ` [PATCH 17/19] ARM: OMAP3+: SmartReflex: misc cleanups Jean Pihet
2012-01-31 9:58 ` [PATCH 18/19] ARM: OMAP3+: SmartReflex: micro-optimization for sanity check Jean Pihet
2012-01-31 9:58 ` [PATCH 19/19] ARM: OMAP3+: SmartReflex: fix the use of debugfs_create_* API Jean Pihet
2012-01-31 17:08 ` Tony Lindgren [this message]
2012-01-31 17:15 ` [PATCH v2 00/19] ARM: OMAP3+: SmartReflex: bugfixes Pihet-XID, Jean
2012-01-31 17:20 ` Tony Lindgren
2012-01-31 17:24 ` Jean Pihet
2012-01-31 17:33 ` Tony Lindgren
2012-01-31 21:59 ` Kevin Hilman
2012-01-31 23:58 ` Tony Lindgren
2012-02-01 8:54 ` Jean Pihet
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=20120131170830.GJ9339@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).