From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Silviu-Mihai Popescu <silviupopescu1990@gmail.com>,
cpufreq@vger.kernel.org, andrew@lunn.ch, jason@lakedaemon.net,
rob.lee@linaro.org, len.brown@intel.com, khilman@ti.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kirkwood: fix coccicheck warnings
Date: Mon, 11 Mar 2013 18:03:24 +0100 [thread overview]
Message-ID: <9281321.Y04oYVrc0i@vostro.rjw.lan> (raw)
In-Reply-To: <1363013700.2291.83.camel@rzhang1-mobl4>
On Monday, March 11, 2013 10:55:00 PM Zhang Rui wrote:
> On Mon, 2013-03-11 at 09:35 +0200, Silviu-Mihai Popescu wrote:
> > Convert all uses of devm_request_and_ioremap() to the newly introduced
> > devm_ioremap_resource() which provides more consistent error handling.
> >
> > devm_ioremap_resource() provides its own error messages so all explicit
> > error messages can be removed from the failure code paths.
> >
> > Signed-off-by: Silviu-Mihai Popescu <silviupopescu1990@gmail.com>
> > ---
> > drivers/cpufreq/kirkwood-cpufreq.c | 8 +++-----
> > drivers/cpuidle/cpuidle-kirkwood.c | 6 +++---
> > drivers/thermal/kirkwood_thermal.c | 8 +++-----
> > 3 files changed, 9 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/cpufreq/kirkwood-cpufreq.c b/drivers/cpufreq/kirkwood-cpufreq.c
> > index 0e83e3c..6052476 100644
> > --- a/drivers/cpufreq/kirkwood-cpufreq.c
> > +++ b/drivers/cpufreq/kirkwood-cpufreq.c
> > @@ -175,11 +175,9 @@ static int kirkwood_cpufreq_probe(struct platform_device *pdev)
> > dev_err(&pdev->dev, "Cannot get memory resource\n");
> > return -ENODEV;
> > }
> > - priv.base = devm_request_and_ioremap(&pdev->dev, res);
> > - if (!priv.base) {
> > - dev_err(&pdev->dev, "Cannot ioremap\n");
> > - return -EADDRNOTAVAIL;
> > - }
> > + priv.base = devm_ioremap_resource(&pdev->dev, res);
> > + if (IS_ERR(priv.base))
> > + return PTR_ERR(priv.base);
> >
> > np = of_find_node_by_path("/cpus/cpu@0");
> > if (!np)
> > diff --git a/drivers/cpuidle/cpuidle-kirkwood.c b/drivers/cpuidle/cpuidle-kirkwood.c
> > index 670aa1e..53aad73 100644
> > --- a/drivers/cpuidle/cpuidle-kirkwood.c
> > +++ b/drivers/cpuidle/cpuidle-kirkwood.c
> > @@ -66,9 +66,9 @@ static int kirkwood_cpuidle_probe(struct platform_device *pdev)
> > if (res == NULL)
> > return -EINVAL;
> >
> > - ddr_operation_base = devm_request_and_ioremap(&pdev->dev, res);
> > - if (!ddr_operation_base)
> > - return -EADDRNOTAVAIL;
> > + ddr_operation_base = devm_ioremap_resource(&pdev->dev, res);
> > + if (IS_ERR(ddr_operation_base))
> > + return PTR_ERR(ddr_operation_base);
> >
> > device = &per_cpu(kirkwood_cpuidle_device, smp_processor_id());
> > device->state_count = KIRKWOOD_MAX_STATES;
> > diff --git a/drivers/thermal/kirkwood_thermal.c b/drivers/thermal/kirkwood_thermal.c
> > index 65cb4f0..e5500ed 100644
> > --- a/drivers/thermal/kirkwood_thermal.c
> > +++ b/drivers/thermal/kirkwood_thermal.c
> > @@ -85,11 +85,9 @@ static int kirkwood_thermal_probe(struct platform_device *pdev)
> > if (!priv)
> > return -ENOMEM;
> >
> > - priv->sensor = devm_request_and_ioremap(&pdev->dev, res);
> > - if (!priv->sensor) {
> > - dev_err(&pdev->dev, "Failed to request_ioremap memory\n");
> > - return -EADDRNOTAVAIL;
> > - }
> > + priv->sensor = devm_ioremap_resource(&pdev->dev, res);
> > + if (IS_ERR(priv->sensor))
> > + return PTR_ERR(priv->sensor);
> >
> > thermal = thermal_zone_device_register("kirkwood_thermal", 0, 0,
> > priv, &ops, NULL, 0, 0);
>
> there is already a fix for kirkwood_thermal.c at
> http://marc.info/?l=linux-pm&m=136238017027514&w=2
> and it has been applied to thermal -next.
>
> would you please refreshed the patch?
Are you going to take that patch into your tree, then?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-03-11 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 7:35 [PATCH] kirkwood: fix coccicheck warnings Silviu-Mihai Popescu
2013-03-11 7:56 ` Andrew Lunn
2013-03-11 13:46 ` Jason Cooper
2013-03-11 13:49 ` Viresh Kumar
2013-03-11 14:55 ` Zhang Rui
2013-03-11 17:03 ` Rafael J. Wysocki [this message]
2013-03-11 17:02 ` Silviu Popescu
2013-03-11 23:58 ` Zhang Rui
2013-03-12 0:10 ` Rafael J. Wysocki
2013-03-21 23:48 ` Rafael J. Wysocki
2013-03-22 0:18 ` Silviu Popescu
2013-03-22 0:43 ` Rafael J. Wysocki
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=9281321.Y04oYVrc0i@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=andrew@lunn.ch \
--cc=cpufreq@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rob.lee@linaro.org \
--cc=rui.zhang@intel.com \
--cc=silviupopescu1990@gmail.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