From: Jingoo Han <jg1.han@samsung.com>
To: "'Mark Brown'" <broonie@kernel.org>
Cc: "'Liam Girdwood'" <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
"'Jingoo Han'" <jg1.han@samsung.com>,
"'Haojian Zhuang'" <haojian.zhuang@gmail.com>
Subject: [PATCH 2/3] regulator: max8649: remove unnecessary OOM messages
Date: Mon, 02 Jun 2014 15:29:57 +0900 [thread overview]
Message-ID: <000201cf7e2c$129996b0$37ccc410$%han@samsung.com> (raw)
In-Reply-To: <000101cf7e2b$b5c9f9c0$215ded40$%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/regulator/max8649.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/max8649.c b/drivers/regulator/max8649.c
index 3172da8..c8bddcc 100644
--- a/drivers/regulator/max8649.c
+++ b/drivers/regulator/max8649.c
@@ -161,10 +161,8 @@ static int max8649_regulator_probe(struct i2c_client *client,
info = devm_kzalloc(&client->dev, sizeof(struct max8649_regulator_info),
GFP_KERNEL);
- if (!info) {
- dev_err(&client->dev, "No enough memory\n");
+ if (!info)
return -ENOMEM;
- }
info->regmap = devm_regmap_init_i2c(client, &max8649_regmap_config);
if (IS_ERR(info->regmap)) {
--
1.7.10.4
next prev parent reply other threads:[~2014-06-02 6:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 6:27 [PATCH 1/3] regulator: bcm590xx: " Jingoo Han
2014-06-02 6:29 ` Jingoo Han [this message]
2014-06-02 14:12 ` [PATCH 2/3] regulator: max8649: " 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'
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='000201cf7e2c$129996b0$37ccc410$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=broonie@kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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 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®