linux-kernel - Re: [PATCH V2 4/4] PM / OPP: Create separate structure for regulator/supplies

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] [day] [month] [year] [list]

Message-ID: <20151028083739.GG30039@ubuntu>
Date:	Wed, 28 Oct 2015 14:07:39 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Rafael Wysocki <rjw@...ysocki.net>
Cc:	linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org,
	sboyd@...eaurora.org, nm@...com,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Dmitry Torokhov <dtor@...omium.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Len Brown <len.brown@...el.com>,
	open list <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@....cz>
Subject: Re: [PATCH V2 4/4] PM / OPP: Create separate structure for
 regulator/supplies

On 15-10-15, 21:42, Viresh Kumar wrote:
> Support for multiple regulators will be added later, until then move
> all power-supply related information in a separate structure.
> 
> To make allocating/freeing memory for these supply structures easy,
> allocate memory for them along with opp.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
>  drivers/base/power/opp/core.c | 57 ++++++++++++++++++++++++++++---------------
>  drivers/base/power/opp/opp.h  | 29 ++++++++++++++++------
>  2 files changed, 58 insertions(+), 28 deletions(-)

Please drop this patch for now, I will get it included in the
multi-regulator series later.

-- 
viresh
--
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/