All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: "Pillai, Manikandan" <mani.pillai@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/2] Include TPS6235x based Power regulator support
Date: Wed, 14 Jan 2009 10:40:22 -0800	[thread overview]
Message-ID: <200901141040.22889.david-b@pacbell.net> (raw)
In-Reply-To: <20090114181035.GC8108@sirena.org.uk>

On Wednesday 14 January 2009, Mark Brown wrote:
> On Wed, Jan 14, 2009 at 09:55:58AM -0800, David Brownell wrote:
> 
> > problem vanishes.  Only the tps6235x.c driver, and in this case
> > the regulator framework (sigh), care about that platform_data. 
> 
> The regulator framework will be fixed in .30.

That'll be nice, thanks.  Good to be consistent, and
stick to the policy that platform_data is *only* for
use by the device's driver.

- Dave

  reply	other threads:[~2009-01-14 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  7:41 [PATCH 1/2] Include TPS6235x based Power regulator support Manikandan Pillai
2009-01-13 21:15 ` Mark Brown
2009-01-13 22:07 ` Mark Brown
2009-01-14 10:02   ` Pillai, Manikandan
2009-01-14 11:01     ` Mark Brown
2009-01-14 11:04       ` Pillai, Manikandan
2009-01-14 11:57         ` Mark Brown
2009-01-14 18:21         ` David Brownell
2009-01-14 18:16     ` David Brownell
2009-01-14  0:19 ` David Brownell
2009-01-14 10:39   ` Pillai, Manikandan
2009-01-14 11:48     ` Mark Brown
2009-01-14 17:55     ` David Brownell
2009-01-14 18:10       ` Mark Brown
2009-01-14 18:40         ` David Brownell [this message]
     [not found]   ` <200901201106.00914.david-b@pacbell.net>
2009-01-20 20:28     ` Mark Brown

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=200901141040.22889.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=broonie@sirena.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=mani.pillai@ti.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.