All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Rajendra Nayak <rnayak@ti.com>, linux-omap@vger.kernel.org
Cc: tony@atomide.com, linux-arm-kernel@lists.infradead.org,
	Felipe Balbi <balbi@ti.com>
Subject: RE: [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp
Date: Wed, 16 Feb 2011 17:49:03 +0530	[thread overview]
Message-ID: <147642dc9bed7d0af86fc618cca09edd@mail.gmail.com> (raw)
In-Reply-To: <1296737122-20765-1-git-send-email-rnayak@ti.com>

Tony,

> -----Original Message-----
> From: Rajendra Nayak [mailto:rnayak@ti.com]
> Sent: Thursday, February 03, 2011 6:15 PM
> To: linux-omap@vger.kernel.org
> Cc: tony@atomide.com; linux-arm-kernel@lists.infradead.org;
balbi@ti.com; Rajendra Nayak
> Subject: [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp
>
> This is a short series to fix some, and clean the
> existing regulator consumer supply mappings for
> the OMAP3430sdp board.
>
> The series is boot tested on the 3430sdp board
> and applies on 2.6.38-rc3.

Any plans to pull these 3430sdp board file cleanup/fixes?

Regards,
Rajendra

>
> Changes in v2:
> Define regulator_consumer_supply as array's
> and use ARRAY_SIZE macro to define
> num_consumer_supplies
>
> Rajendra Nayak (2):
>   omap3sdp: Fix regulator mapping for ads7846 TS controller
>   omap3sdp: clean regulator supply mapping in board file
>
>  arch/arm/mach-omap2/board-3430sdp.c |   78
+++++++++++++++++------------------
>  1 files changed, 38 insertions(+), 40 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp
Date: Wed, 16 Feb 2011 17:49:03 +0530	[thread overview]
Message-ID: <147642dc9bed7d0af86fc618cca09edd@mail.gmail.com> (raw)
In-Reply-To: <1296737122-20765-1-git-send-email-rnayak@ti.com>

Tony,

> -----Original Message-----
> From: Rajendra Nayak [mailto:rnayak at ti.com]
> Sent: Thursday, February 03, 2011 6:15 PM
> To: linux-omap at vger.kernel.org
> Cc: tony at atomide.com; linux-arm-kernel at lists.infradead.org;
balbi at ti.com; Rajendra Nayak
> Subject: [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp
>
> This is a short series to fix some, and clean the
> existing regulator consumer supply mappings for
> the OMAP3430sdp board.
>
> The series is boot tested on the 3430sdp board
> and applies on 2.6.38-rc3.

Any plans to pull these 3430sdp board file cleanup/fixes?

Regards,
Rajendra

>
> Changes in v2:
> Define regulator_consumer_supply as array's
> and use ARRAY_SIZE macro to define
> num_consumer_supplies
>
> Rajendra Nayak (2):
>   omap3sdp: Fix regulator mapping for ads7846 TS controller
>   omap3sdp: clean regulator supply mapping in board file
>
>  arch/arm/mach-omap2/board-3430sdp.c |   78
+++++++++++++++++------------------
>  1 files changed, 38 insertions(+), 40 deletions(-)

  parent reply	other threads:[~2011-02-16 12:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 12:45 [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp Rajendra Nayak
2011-02-03 12:45 ` Rajendra Nayak
2011-02-03 12:45 ` [PATCH v2 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller Rajendra Nayak
2011-02-03 12:45   ` Rajendra Nayak
2011-02-03 12:45   ` [PATCH v2 2/2] omap3sdp: clean regulator supply mapping in board file Rajendra Nayak
2011-02-03 12:45     ` Rajendra Nayak
2011-02-03 12:54     ` Felipe Balbi
2011-02-03 12:54       ` Felipe Balbi
2011-02-03 12:54   ` [PATCH v2 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller Felipe Balbi
2011-02-03 12:54     ` Felipe Balbi
2011-02-16 12:19 ` Rajendra Nayak [this message]
2011-02-16 12:19   ` [PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp Rajendra Nayak
2011-02-17 23:49 ` Tony Lindgren
2011-02-17 23:49   ` Tony Lindgren

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=147642dc9bed7d0af86fc618cca09edd@mail.gmail.com \
    --to=rnayak@ti.com \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.