public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: "'Daniel Lezcano'" <daniel.lezcano@linaro.org>
Cc: "'Thomas Gleixner'" <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	"'Jingoo Han'" <jg1.han@samsung.com>,
	"'Magnus Damm'" <damm@opensource.se>
Subject: [PATCH 2/4] clocksource: sh_cmt: remove unnecessary OOM messages
Date: Tue, 29 Apr 2014 17:27:03 +0900	[thread overview]
Message-ID: <002e01cf6384$cc7ef920$657ceb60$%han@samsung.com> (raw)
In-Reply-To: <002c01cf6384$781c57b0$68550710$%han@samsung.com>

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/clocksource/sh_cmt.c |    4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/drivers/clocksource/sh_cmt.c b/drivers/clocksource/sh_cmt.c
index 0b1836a..d2aa209 100644
--- a/drivers/clocksource/sh_cmt.c
+++ b/drivers/clocksource/sh_cmt.c
@@ -824,10 +824,8 @@ static int sh_cmt_probe(struct platform_device *pdev)
 	}
 
 	p = kmalloc(sizeof(*p), GFP_KERNEL);
-	if (p == NULL) {
-		dev_err(&pdev->dev, "failed to allocate driver data\n");
+	if (p == NULL)
 		return -ENOMEM;
-	}
 
 	ret = sh_cmt_setup(p, pdev);
 	if (ret) {
-- 
1.7.10.4



  parent reply	other threads:[~2014-04-29  8:27 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
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 ` Jingoo Han [this message]
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='002e01cf6384$cc7ef920$657ceb60$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=damm@opensource.se \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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