[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <515AD8BC.5050206@stericsson.com>
Date: Tue, 2 Apr 2013 15:10:20 +0200
From: Bengt Jönsson <bengt.g.jonsson@...ricsson.com>
To: Axel Lin <axel.lin@...ics.com>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Lee Jones <lee.jones@...aro.org>,
Yvan FILLION <yvan.fillion@...ricsson.com>,
Liam Girdwood <lgirdwood@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: dbx500-prcmu: Remove operating_point from
struct dbx500_regulator_info
On 04/02/2013 03:08 PM, Axel Lin wrote:
> operating_point is not used since the initial commit of db8500-prcmu driver,
> remove it.
>
> Signed-off-by: Axel Lin <axel.lin@...ics.com>
Acked-by: Bengt Jonsson <bengt.g.jonsson@...ricsson.com>
> ---
> drivers/regulator/dbx500-prcmu.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/regulator/dbx500-prcmu.h b/drivers/regulator/dbx500-prcmu.h
> index e763883..c8e51ac 100644
> --- a/drivers/regulator/dbx500-prcmu.h
> +++ b/drivers/regulator/dbx500-prcmu.h
> @@ -21,7 +21,6 @@
> * @is_enabled: status of the regulator
> * @epod_id: id for EPOD (power domain)
> * @is_ramret: RAM retention switch for EPOD (power domain)
> - * @operating_point: operating point (only for vape, to be removed)
> *
> */
> struct dbx500_regulator_info {
> @@ -32,7 +31,6 @@ struct dbx500_regulator_info {
> u16 epod_id;
> bool is_ramret;
> bool exclude_from_power_state;
> - unsigned int operating_point;
> };
>
> void power_state_active_enable(void);
--
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/
Powered by blists - more mailing lists