All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: green@linuxhacker.ru
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Mike Rapoport <mike@compulab.co.il>,
	Nishant Kamat <nskamat@ti.com>, Steve Sakoman <steve@sakoman.com>,
	Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH 1/2] cleanup regulator supply definitions in mach-omap2 to use REGULATOR_SUPPLY
Date: Mon, 06 Jun 2011 12:18:47 +0530	[thread overview]
Message-ID: <4DEC784F.9060503@ti.com> (raw)
In-Reply-To: <1307342762-25363-2-git-send-email-green@linuxhacker.ru>

On 6/6/2011 12:16 PM, green@linuxhacker.ru wrote:
> From: Oleg Drokin<green@linuxhacker.ru>
>
> CC: Mark Brown<broonie@opensource.wolfsonmicro.com>
> CC: Mike Rapoport<mike@compulab.co.il>
> CC: Nishant Kamat<nskamat@ti.com>
> CC: Steve Sakoman<steve@sakoman.com>
> CC: Felipe Balbi<balbi@ti.com>
> CC: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Signed-off-by: Oleg Drokin<green@linuxhacker.ru>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>	

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] cleanup regulator supply definitions in mach-omap2 to use REGULATOR_SUPPLY
Date: Mon, 06 Jun 2011 12:18:47 +0530	[thread overview]
Message-ID: <4DEC784F.9060503@ti.com> (raw)
In-Reply-To: <1307342762-25363-2-git-send-email-green@linuxhacker.ru>

On 6/6/2011 12:16 PM, green at linuxhacker.ru wrote:
> From: Oleg Drokin<green@linuxhacker.ru>
>
> CC: Mark Brown<broonie@opensource.wolfsonmicro.com>
> CC: Mike Rapoport<mike@compulab.co.il>
> CC: Nishant Kamat<nskamat@ti.com>
> CC: Steve Sakoman<steve@sakoman.com>
> CC: Felipe Balbi<balbi@ti.com>
> CC: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Signed-off-by: Oleg Drokin<green@linuxhacker.ru>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>	

  reply	other threads:[~2011-06-06  6:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  6:46 Regulator cleanups in mach-omap2, take two green
2011-06-06  6:46 ` [PATCH 1/2] cleanup regulator supply definitions in mach-omap2 to use REGULATOR_SUPPLY green
2011-06-06  6:48   ` Santosh Shilimkar [this message]
2011-06-06  6:48     ` Santosh Shilimkar
2011-06-06  9:21   ` Felipe Balbi
2011-06-06  9:21     ` Felipe Balbi
2011-06-06 15:45     ` Oleg Drokin
2011-06-06 15:45       ` Oleg Drokin
2011-06-06 17:13       ` Felipe Balbi
2011-06-06 17:13         ` Felipe Balbi
2011-06-06 17:18         ` Oleg Drokin
2011-06-06 17:18           ` Oleg Drokin
2011-06-06 17:28           ` Felipe Balbi
2011-06-06 17:28             ` Felipe Balbi
2011-06-06 17:36             ` Oleg Drokin
2011-06-06 17:36               ` Oleg Drokin
2011-06-06  6:46 ` [PATCH 2/2] Remove old-style supply.dev assignments common in hsmmc init green
2011-06-06  9:22   ` Felipe Balbi
2011-06-06  9:22     ` Felipe Balbi
2011-06-06 10:13   ` Grazvydas Ignotas
2011-06-06 10:13     ` Grazvydas Ignotas

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=4DEC784F.9060503@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=balbi@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=green@linuxhacker.ru \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=nskamat@ti.com \
    --cc=steve@sakoman.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.