All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bengt Jönsson" <bengt.g.jonsson@stericsson.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Lee Jones <lee.jones@linaro.org>,
	Yvan FILLION <yvan.fillion@stericsson.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: dbx500-prcmu: Remove operating_point from struct dbx500_regulator_info
Date: Tue, 2 Apr 2013 15:10:20 +0200	[thread overview]
Message-ID: <515AD8BC.5050206@stericsson.com> (raw)
In-Reply-To: <1364908104.9803.3.camel@phoenix>

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@ingics.com>
Acked-by: Bengt Jonsson <bengt.g.jonsson@stericsson.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);


  reply	other threads:[~2013-04-02 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 13:08 [PATCH] regulator: dbx500-prcmu: Remove operating_point from struct dbx500_regulator_info Axel Lin
2013-04-02 13:10 ` Bengt Jönsson [this message]
2013-04-02 22: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=515AD8BC.5050206@stericsson.com \
    --to=bengt.g.jonsson@stericsson.com \
    --cc=axel.lin@ingics.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yvan.fillion@stericsson.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.