linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Anuj Aggarwal <anuj.aggarwal@ti.com>,
	Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org, broonie@opensource.wolfsonmicro.com,
	lrg@slimlogic.co.uk
Subject: Re: [PATCHv3 0/4] Regulator: OMAP: Removing common code for TWL4030 from OMAP3-board-evms
Date: Fri, 14 May 2010 12:33:12 -0700	[thread overview]
Message-ID: <20100514193312.GB3428@atomide.com> (raw)
In-Reply-To: <1267525723-3068-1-git-send-email-anuj.aggarwal@ti.com>

* Anuj Aggarwal <anuj.aggarwal@ti.com> [100302 02:25]:
> Sending version 3 of this patch-set after rebasing it against the for-next
> branch in the linux-omap tree. The previous series can be found at:
>   http://marc.info/?l=linux-omap&m=126328763822497&w=2
> 
> This patch set is created to clean up various OMAP3-board-evm files
> and remove common TWL4030 specific regulator suplies and init data
> structs. These structures are instead placed in a new generic file -
> twl4030-pmic.c - and are referenced from the OMAP3 board-evm
> files depending on the platform requirements. Regulator having specific
> supplies or init data structs are not changed in their respective
> board-evms.
> 
> uImage built and tested for OMAP3EVM; compile-tested for SDP3430 and all OMAP
> platforms (using omap3_defconfig).
> 
> Anuj Aggarwal (4):
>   Regulator: OMAP: Creating TWL4030 file having supplies & init data
>   Regulator: OMAP: Modifying Kconfig/Makefile to choose from available
>     PMICs
>   Regulator: OMAP: Kconfig modified to select TWL4030 for
>     OMAP3-platforms
>   Regulator: OMAP: Use common regulator supplies and init data structs
> 
>  arch/arm/mach-omap2/Kconfig                  |   20 +++
>  arch/arm/mach-omap2/Makefile                 |    1 +
>  arch/arm/mach-omap2/board-3430sdp.c          |  135 ++------------------
>  arch/arm/mach-omap2/board-cm-t35.c           |   47 +------
>  arch/arm/mach-omap2/board-igep0020.c         |   24 +---
>  arch/arm/mach-omap2/board-ldp.c              |   24 +---
>  arch/arm/mach-omap2/board-omap3beagle.c      |   47 +------
>  arch/arm/mach-omap2/board-omap3evm.c         |   47 +------
>  arch/arm/mach-omap2/board-omap3touchbook.c   |   47 +------
>  arch/arm/mach-omap2/board-overo.c            |   23 +---
>  arch/arm/mach-omap2/board-zoom-peripherals.c |   71 +----------
>  arch/arm/mach-omap2/twl4030-pmic.c           |  175 ++++++++++++++++++++++++++
>  arch/arm/mach-omap2/twl4030-pmic.h           |   34 +++++
>  13 files changed, 277 insertions(+), 418 deletions(-)
>  create mode 100644 arch/arm/mach-omap2/twl4030-pmic.c
>  create mode 100644 arch/arm/mach-omap2/twl4030-pmic.h

Are these patches still relevant?

I'd like to see some acks on these..

Regards,

Tony 

      reply	other threads:[~2010-05-14 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 10:28 [PATCHv3 0/4] Regulator: OMAP: Removing common code for TWL4030 from OMAP3-board-evms Anuj Aggarwal
2010-05-14 19:33 ` Tony Lindgren [this message]

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=20100514193312.GB3428@atomide.com \
    --to=tony@atomide.com \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=peter.de-schrijver@nokia.com \
    /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).