From: "'Matt Porter'" <mporter@linaro.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Mark Brown'" <broonie@kernel.org>,
"'Liam Girdwood'" <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
"'Tim Kryger'" <tim.kryger@linaro.org>
Subject: Re: [PATCH 1/3] regulator: bcm590xx: remove unnecessary OOM messages
Date: Tue, 3 Jun 2014 11:19:15 -0400 [thread overview]
Message-ID: <20140603151915.GV32082@beef> (raw)
In-Reply-To: <000101cf7e2b$b5c9f9c0$215ded40$%han@samsung.com>
On Mon, Jun 02, 2014 at 03:27:21PM +0900, Jingoo Han wrote:
> The site-specific OOM messages are unnecessary, because they
> duplicate the MM subsystem generic OOM message.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/regulator/bcm590xx-regulator.c | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
Looks good, thanks.
Acked-by: Matt Porter <mporter@linaro.org>
> diff --git a/drivers/regulator/bcm590xx-regulator.c b/drivers/regulator/bcm590xx-regulator.c
> index 57544e2..fb8c6f7 100644
> --- a/drivers/regulator/bcm590xx-regulator.c
> +++ b/drivers/regulator/bcm590xx-regulator.c
> @@ -326,10 +326,8 @@ static struct bcm590xx_board *bcm590xx_parse_dt_reg_data(
> }
>
> data = devm_kzalloc(&pdev->dev, sizeof(*data), GFP_KERNEL);
> - if (!data) {
> - dev_err(&pdev->dev, "failed to allocate regulator board data\n");
> + if (!data)
> return NULL;
> - }
>
> np = of_node_get(np);
> regulators = of_get_child_by_name(np, "regulators");
> @@ -374,10 +372,8 @@ static int bcm590xx_probe(struct platform_device *pdev)
> &bcm590xx_reg_matches);
>
> pmu = devm_kzalloc(&pdev->dev, sizeof(*pmu), GFP_KERNEL);
> - if (!pmu) {
> - dev_err(&pdev->dev, "Memory allocation failed for pmu\n");
> + if (!pmu)
> return -ENOMEM;
> - }
>
> pmu->mfd = bcm590xx;
>
> @@ -385,17 +381,13 @@ static int bcm590xx_probe(struct platform_device *pdev)
>
> pmu->desc = devm_kzalloc(&pdev->dev, BCM590XX_NUM_REGS *
> sizeof(struct regulator_desc), GFP_KERNEL);
> - if (!pmu->desc) {
> - dev_err(&pdev->dev, "Memory alloc fails for desc\n");
> + if (!pmu->desc)
> return -ENOMEM;
> - }
>
> pmu->info = devm_kzalloc(&pdev->dev, BCM590XX_NUM_REGS *
> sizeof(struct bcm590xx_info *), GFP_KERNEL);
> - if (!pmu->info) {
> - dev_err(&pdev->dev, "Memory alloc fails for info\n");
> + if (!pmu->info)
> return -ENOMEM;
> - }
>
> info = bcm590xx_regs;
>
> --
> 1.7.10.4
>
>
next prev parent reply other threads:[~2014-06-03 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 6:27 [PATCH 1/3] regulator: bcm590xx: remove unnecessary OOM messages Jingoo Han
2014-06-02 6:29 ` [PATCH 2/3] regulator: max8649: " Jingoo Han
2014-06-02 14:12 ` Mark Brown
2014-06-02 6:30 ` [PATCH 3/3] regulator: pbias: " Jingoo Han
2014-06-02 14:15 ` Mark Brown
2014-06-02 7:12 ` [PATCH 1/3] regulator: bcm590xx: " Tim Kryger
2014-06-02 12:50 ` Mark Brown
2014-06-03 6:41 ` Tim Kryger
2014-06-03 10:05 ` Mark Brown
2014-06-03 15:19 ` 'Matt Porter' [this message]
2014-06-06 10:08 ` 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=20140603151915.GV32082@beef \
--to=mporter@linaro.org \
--cc=broonie@kernel.org \
--cc=jg1.han@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.kryger@linaro.org \
/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.