public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Thomas Gleixner'" <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	"'Shinya Kuribayashi'" <shinya.kuribayashi.px@renesas.com>,
	"'Magnus Damm'" <damm@opensource.se>
Subject: Re: [PATCH 1/4] clocksource: em_sti: remove unnecessary OOM messages
Date: Mon, 19 May 2014 12:48:23 +0200	[thread overview]
Message-ID: <5379E177.2030707@linaro.org> (raw)
In-Reply-To: <002d01cf6384$a6dbcf90$f4936eb0$%han@samsung.com>

On 04/29/2014 10:26 AM, Jingoo Han wrote:
> The site-specific OOM messages are unnecessary, because they
> duplicate the MM subsystem generic OOM message.

Are you sure the MM subsys display a message when an allocation fails ?

There are multiple reasons an allocation can fail.

> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
>   drivers/clocksource/em_sti.c |    4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/clocksource/em_sti.c b/drivers/clocksource/em_sti.c
> index 9d17083..d0a7bd6 100644
> --- a/drivers/clocksource/em_sti.c
> +++ b/drivers/clocksource/em_sti.c
> @@ -318,10 +318,8 @@ static int em_sti_probe(struct platform_device *pdev)
>   	int irq;
>
>   	p = devm_kzalloc(&pdev->dev, sizeof(*p), GFP_KERNEL);
> -	if (p == NULL) {
> -		dev_err(&pdev->dev, "failed to allocate driver data\n");
> +	if (p == NULL)
>   		return -ENOMEM;
> -	}
>
>   	p->pdev = pdev;
>   	platform_set_drvdata(pdev, p);
>


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2014-05-19 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  8:24 [PATCH 0/4] clocksource: remove unnecessary OOM messages Jingoo Han
2014-04-29  8:26 ` [PATCH 1/4] clocksource: em_sti: " Jingoo Han
2014-05-19 10:48   ` Daniel Lezcano [this message]
2014-05-22  4:55     ` Jingoo Han
2014-05-22  7:27       ` Dan Carpenter
2014-05-22 11:54       ` Daniel Lezcano
2014-04-29  8:27 ` [PATCH 2/4] clocksource: sh_cmt: " Jingoo Han
2014-04-29  8:27 ` [PATCH 3/4] clocksource: sh_mtu2: " Jingoo Han
2014-04-29  8:28 ` [PATCH 4/4] clocksource: sh_tmu: " Jingoo Han
2014-05-22 12:06 ` [PATCH 0/4] clocksource: " Daniel Lezcano

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=5379E177.2030707@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=damm@opensource.se \
    --cc=jg1.han@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shinya.kuribayashi.px@renesas.com \
    --cc=tglx@linutronix.de \
    /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