linux-kernel - Re: [PATCH] mfd: twl-core: Don't specify regulator consumers by struct device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120203180850.GB17584@sortiz-mobl>
Date:	Fri, 3 Feb 2012 19:08:50 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Peter Ujfalusi <peter.ujfalusi@...com>,
	Balaji T K <balajitk@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: twl-core: Don't specify regulator consumers by
 struct device

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@...b.auug.org.au>
> Signed-off-by: Mark Brown <broonie@...nsource.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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/