mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Balaji T K <balajitk@ti.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: twl-core: Don't specify regulator consumers by struct device
Date: Fri, 3 Feb 2012 19:08:50 +0100	[thread overview]
Message-ID: <20120203180850.GB17584@sortiz-mobl> (raw)
In-Reply-To: <1328267137-4816-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Hi Mark,

On Fri, Feb 03, 2012 at 11:05:37AM +0000, Mark Brown wrote:
> This has been deprecated for considerable time now and support has been
> removed from the regulator API. dev_name should be used instead.
Thanks for the quick fix. I applied this one to my for-next branch as well.


> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> 
> I'll apply this to the regulator tree as it's thrown up issues due to
> the removal of dev from regulator_consumer_supply - please let me know
> if this is an issue, I can back it out easily enough.
When did the regulator API get modified ? During the last merge window, or is
this one something Linus should be pulling ASAP ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  parent reply	other threads:[~2012-02-03 18:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 11:05 Mark Brown
2012-02-03 11:29 ` Peter Ujfalusi
2012-02-03 18:08 ` Samuel Ortiz [this message]
2012-02-03 19:05   ` 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=20120203180850.GB17584@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=balajitk@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®