All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org, nsekhar@ti.com
Subject: Re: [PATCH V4 2/2] regulator: tps65217: Add tps65217 regulator driver
Date: Sun, 15 Jan 2012 12:20:10 +0000	[thread overview]
Message-ID: <20120115122009.GF3040@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1326278509-31310-1-git-send-email-anilkumar@ti.com>

On Wed, Jan 11, 2012 at 04:11:49PM +0530, AnilKumar Ch wrote:

> +	rdev = regulator_register(&regulators[pdev->id], &pdev->dev,
> +				  pdev->dev.platform_data, tps);

Oh, actually - this needs redoing against -next, regulator_register now
takes an additional of_node argument.  If there's no device tree support
it can be null.

      parent reply	other threads:[~2012-01-15 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 10:41 [PATCH V4 2/2] regulator: tps65217: Add tps65217 regulator driver AnilKumar Ch
2012-01-11 10:41 ` AnilKumar Ch
2012-01-15 12:16 ` Mark Brown
2012-01-15 12:20 ` Mark Brown [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=20120115122009.GF3040@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=anilkumar@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=nsekhar@ti.com \
    --cc=sameo@linux.intel.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.