From: Jingoo Han <jg1.han@samsung.com>
To: 'Thierry Reding' <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, 'Jingoo Han' <jg1.han@samsung.com>
Subject: [PATCH RESEND 7/9] pwm: pwm-tiecap: Remove unnecessary OOM messages
Date: Wed, 23 Apr 2014 18:41:27 +0900 [thread overview]
Message-ID: <001101cf5ed8$32fe30a0$98fa91e0$%han@samsung.com> (raw)
In-Reply-To: <000a01cf5ed7$bd178ad0$3746a070$%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/pwm/pwm-tiecap.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/pwm/pwm-tiecap.c b/drivers/pwm/pwm-tiecap.c
index 032092c..74efbe7 100644
--- a/drivers/pwm/pwm-tiecap.c
+++ b/drivers/pwm/pwm-tiecap.c
@@ -209,10 +209,8 @@ static int ecap_pwm_probe(struct platform_device *pdev)
u16 status;
pc = devm_kzalloc(&pdev->dev, sizeof(*pc), GFP_KERNEL);
- if (!pc) {
- dev_err(&pdev->dev, "failed to allocate memory\n");
+ if (!pc)
return -ENOMEM;
- }
clk = devm_clk_get(&pdev->dev, "fck");
if (IS_ERR(clk)) {
--
1.7.10.4
next prev parent reply other threads:[~2014-04-23 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 9:38 [PATCH RESEND 0/9] pwm: Remove unnecessary OOM messages Jingoo Han
2014-04-23 9:39 ` [PATCH RESEND 1/9] pwm: ab8500: " Jingoo Han
2014-04-23 9:39 ` [PATCH RESEND 2/9] pwm: i.MX: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 3/9] pwm: pxa: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 4/9] pwm: renesas-tpu: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 5/9] pwm: spear: " Jingoo Han
2014-04-23 9:41 ` [PATCH RESEND 6/9] pwm: tegra: " Jingoo Han
2014-04-23 9:41 ` Jingoo Han [this message]
2014-04-23 9:41 ` [PATCH RESEND 8/9] pwm: tiehrpwm: " Jingoo Han
2014-04-23 9:42 ` [PATCH RESEND 9/9] pwm: vt8500: " Jingoo Han
2014-04-28 11:42 ` [PATCH RESEND 0/9] pwm: " Thierry Reding
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='001101cf5ed8$32fe30a0$98fa91e0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).