From: Jingoo Han <jg1.han@samsung.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"'Alessandro Zummo'" <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, "'Jingoo Han'" <jg1.han@samsung.com>,
"'Wolfgang Grandegger'" <wg@grandegger.com>
Subject: [PATCH 08/10] rtc: rtc-rx8025: Remove unnecessary OOM messages
Date: Fri, 07 Feb 2014 17:11:08 +0900 [thread overview]
Message-ID: <001101cf23dc$27c876a0$775963e0$%han@samsung.com> (raw)
In-Reply-To: <000901cf23da$a04cbca0$e0e635e0$%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/rtc/rtc-rx8025.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/rtc/rtc-rx8025.c b/drivers/rtc/rtc-rx8025.c
index 8fa23ea..e6298e0 100644
--- a/drivers/rtc/rtc-rx8025.c
+++ b/drivers/rtc/rtc-rx8025.c
@@ -551,7 +551,6 @@ static int rx8025_probe(struct i2c_client *client,
rx8025 = devm_kzalloc(&client->dev, sizeof(*rx8025), GFP_KERNEL);
if (!rx8025) {
- dev_err(&adapter->dev, "failed to alloc memory\n");
err = -ENOMEM;
goto errout;
}
--
1.7.10.4
next prev parent reply other threads:[~2014-02-07 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:00 [PATCH 00/10] rtc: " Jingoo Han
2014-02-07 8:02 ` [PATCH 01/10] rtc: rtc-at32ap700x: " Jingoo Han
2014-02-07 8:04 ` Hans-Christian Egtvedt
2014-02-07 8:02 ` [PATCH 02/10] rtc: rtc-davinci: " Jingoo Han
2014-02-07 8:03 ` [PATCH 03/10] rtc: rtc-ds1390: " Jingoo Han
2014-02-07 8:06 ` [PATCH 05/10] rtc: rtc-moxart: " Jingoo Han
2014-02-07 8:07 ` [PATCH 06/10] rtc: rtc-nuc900: " Jingoo Han
2014-02-07 8:09 ` [PATCH 07/10] rtc: rtc-pm8xxx: " Jingoo Han
2014-02-07 8:11 ` Jingoo Han [this message]
2014-02-07 8:12 ` [PATCH 09/10] rtc: rtc-sirfsoc: " Jingoo Han
2014-02-07 12:08 ` Barry Song
2014-02-07 8:14 ` [PATCH 04/10] rtc: rtc-lpc32xx: " Jingoo Han
2014-02-07 8:15 ` [PATCH 10/10] rtc: rtc-spear: " Jingoo Han
2014-02-07 10:07 ` Viresh Kumar
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='001101cf23dc$27c876a0$775963e0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=wg@grandegger.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
all inboxes | Powered by JetHome®