linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
	Support Opensource <support.opensource@diasemi.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/6] regulator: da9063: remove platform_data support
Date: Tue, 19 Mar 2019 13:49:10 +0100	[thread overview]
Message-ID: <20190319124909.7dj6ns5kkgdj4lop@verge.net.au> (raw)
In-Reply-To: <20190318154759.21978-2-wsa+renesas@sang-engineering.com>

On Mon, Mar 18, 2019 at 04:47:53PM +0100, Wolfram Sang wrote:
> There are no in-kernel users anymore, so remove this outdated interface.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Reviewed-by: Simon Horman <horms+renesas@verge.net.au>

> ---
>  drivers/regulator/da9063-regulator.c | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/drivers/regulator/da9063-regulator.c b/drivers/regulator/da9063-regulator.c
> index 2b0c7a85306a..73c85039d0cf 100644
> --- a/drivers/regulator/da9063-regulator.c
> +++ b/drivers/regulator/da9063-regulator.c
> @@ -730,7 +730,6 @@ static struct da9063_regulators_pdata *da9063_parse_regulators_dt(
>  static int da9063_regulator_probe(struct platform_device *pdev)
>  {
>  	struct da9063 *da9063 = dev_get_drvdata(pdev->dev.parent);
> -	struct da9063_pdata *da9063_pdata = dev_get_platdata(da9063->dev);
>  	struct of_regulator_match *da9063_reg_matches = NULL;
>  	struct da9063_regulators_pdata *regl_pdata;
>  	const struct da9063_dev_model *model;
> @@ -740,11 +739,7 @@ static int da9063_regulator_probe(struct platform_device *pdev)
>  	bool bcores_merged, bmem_bio_merged;
>  	int id, irq, n, n_regulators, ret, val;
>  
> -	regl_pdata = da9063_pdata ? da9063_pdata->regulators_pdata : NULL;
> -
> -	if (!regl_pdata)
> -		regl_pdata = da9063_parse_regulators_dt(pdev,
> -							&da9063_reg_matches);
> +	regl_pdata = da9063_parse_regulators_dt(pdev, &da9063_reg_matches);
>  
>  	if (IS_ERR(regl_pdata) || regl_pdata->n_regulators == 0) {
>  		dev_err(&pdev->dev,
> -- 
> 2.11.0
> 

  reply	other threads:[~2019-03-19 12:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 15:47 [PATCH 0/6] mfd: da9063: remove platform_data Wolfram Sang
2019-03-18 15:47 ` [PATCH 1/6] regulator: da9063: remove platform_data support Wolfram Sang
2019-03-19 12:49   ` Simon Horman [this message]
2019-03-29 10:57   ` Steve Twiss
2019-03-18 15:47 ` [PATCH 2/6] input: da9063_onkey: " Wolfram Sang
2019-03-19 12:49   ` Simon Horman
2019-03-29 10:58   ` Steve Twiss
2019-04-03  9:24     ` Wolfram Sang
2019-03-18 15:47 ` [PATCH 3/6] mfd: da9063: " Wolfram Sang
2019-03-19 12:25   ` Simon Horman
2019-03-25 20:22     ` Wolfram Sang
2019-03-19 12:49   ` Simon Horman
2019-03-29 10:58   ` Steve Twiss
2019-04-03  8:02   ` Lee Jones
2019-03-18 15:47 ` [PATCH 4/6] regulator: da9063: move definitions out of a header into the driver Wolfram Sang
2019-03-19 12:49   ` Simon Horman
2019-03-19 13:01   ` Mark Brown
2019-04-03  9:22     ` Wolfram Sang
2019-04-03 10:07       ` Mark Brown
2019-03-29 11:00   ` Steve Twiss
2019-03-18 15:47 ` [PATCH 5/6] mfd: da9063: remove leftover platform_data definitions Wolfram Sang
2019-03-19 12:49   ` Simon Horman
2019-03-29 11:00   ` Steve Twiss
2019-04-03  8:07   ` Lee Jones
2019-04-03  8:50     ` Wolfram Sang
2019-04-03  9:03       ` Lee Jones
2019-03-18 15:47 ` [PATCH 6/6] regulator: da9063: platform_data is gone, depend on OF Wolfram Sang
2019-03-19 12:50   ` Simon Horman
2019-03-29 11:01   ` Steve Twiss
2019-03-18 16:34 ` [PATCH 0/6] mfd: da9063: remove platform_data Steve Twiss
2019-03-29 11:02 ` Steve Twiss
2019-03-29 11:27   ` Wolfram Sang
2019-03-29 11:28   ` Steve Twiss

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=20190319124909.7dj6ns5kkgdj4lop@verge.net.au \
    --to=horms@verge.net.au \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=support.opensource@diasemi.com \
    --cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).