From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 03/13] soc: samsung: pmu: Remove messages for failed memory allocation
Date: Tue, 17 Jan 2017 13:44:34 +0100 [thread overview]
Message-ID: <1484657084-26227-4-git-send-email-m.szyprowski@samsung.com> (raw)
In-Reply-To: <1484657084-26227-1-git-send-email-m.szyprowski@samsung.com>
Memory subsystem already prints message about failed memory
allocation, there is no need to do it in the driver.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
---
drivers/soc/samsung/exynos-pmu.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/soc/samsung/exynos-pmu.c b/drivers/soc/samsung/exynos-pmu.c
index 1f914e63dcc6..813df6e7292d 100644
--- a/drivers/soc/samsung/exynos-pmu.c
+++ b/drivers/soc/samsung/exynos-pmu.c
@@ -117,10 +117,8 @@ static int exynos_pmu_probe(struct platform_device *pdev)
pmu_context = devm_kzalloc(&pdev->dev,
sizeof(struct exynos_pmu_context),
GFP_KERNEL);
- if (!pmu_context) {
- dev_err(dev, "Cannot allocate memory.\n");
+ if (!pmu_context)
return -ENOMEM;
- }
pmu_context->dev = dev;
pmu_context->pmu_data = of_device_get_match_data(dev);
--
1.9.1
next prev parent reply other threads:[~2017-01-17 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170117124453eucas1p1b812596939db4c4f3298b941555eb05a@eucas1p1.samsung.com>
2017-01-17 12:44 ` [PATCH v2 00/13] Move pad retention control to Exynos pin controller driver Marek Szyprowski
2017-01-17 12:44 ` [PATCH v2 01/13] soc: samsung: pmu: Provide global function to get PMU regmap Marek Szyprowski
2017-01-18 8:31 ` Tomasz Figa
2017-01-17 12:44 ` [PATCH v2 02/13] soc: samsung: pmu: Use of_device_get_match_data helper Marek Szyprowski
2017-01-17 12:44 ` Marek Szyprowski [this message]
2017-01-17 12:44 ` [PATCH v2 04/13] pinctrl: samsung: Document Exynos3250 SoC support Marek Szyprowski
2017-01-17 12:44 ` [PATCH v2 05/13] pinctrl: samsung: Remove messages for failed memory allocation Marek Szyprowski
2017-01-17 12:44 ` [PATCH v2 06/13] pinctrl: samsung: Fix samsung_pinctrl_create_functions return value Marek Szyprowski
2017-01-17 17:36 ` Krzysztof Kozlowski
2017-01-17 12:44 ` [PATCH v2 07/13] pinctrl: samsung: Add missing initconst annotation Marek Szyprowski
2017-01-17 12:44 ` [PATCH v2 08/13] pinctrl: samsung: Remove dead code Marek Szyprowski
2017-01-17 12:44 ` [PATCH v2 09/13] pinctrl: samsung: Use generic of_device_get_match_data helper Marek Szyprowski
2017-01-17 17:38 ` Krzysztof Kozlowski
2017-01-17 12:44 ` [PATCH v2 10/13] pinctrl: samsung: Add infrastructure for pin-bank retention control Marek Szyprowski
2017-01-18 8:36 ` Tomasz Figa
2017-01-17 12:44 ` [PATCH v2 11/13] pinctrl: samsung: Move retention control from mach-exynos to the pinctrl driver Marek Szyprowski
2017-01-17 17:48 ` Krzysztof Kozlowski
2017-01-17 12:44 ` [PATCH v2 12/13] pinctrl: samsung: Move retention control from mach-s5pv210 " Marek Szyprowski
2017-01-17 17:54 ` Krzysztof Kozlowski
2017-01-17 12:44 ` [PATCH v2 13/13] pinctrl: samsung: Replace syscore ops with standard platform device pm_ops Marek Szyprowski
2017-01-18 8:40 ` [PATCH v2 00/13] Move pad retention control to Exynos pin controller driver Tomasz Figa
2017-01-18 10:39 ` Linus Walleij
2017-01-18 12:06 ` Krzysztof Kozlowski
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=1484657084-26227-4-git-send-email-m.szyprowski@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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