Commit 437a6bc4 authored by Peter Griffin's avatar Peter Griffin Committed by Kishon Vijay Abraham I

phy: phy-omap-control: Remove unncessary site specific OOM messages

The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().

Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.
Signed-off-by: default avatarPeter Griffin <peter.griffin@linaro.org>
Signed-off-by: default avatarKishon Vijay Abraham I <kishon@ti.com>
parent 1233f59f
...@@ -295,10 +295,8 @@ static int omap_control_phy_probe(struct platform_device *pdev) ...@@ -295,10 +295,8 @@ static int omap_control_phy_probe(struct platform_device *pdev)
control_phy = devm_kzalloc(&pdev->dev, sizeof(*control_phy), control_phy = devm_kzalloc(&pdev->dev, sizeof(*control_phy),
GFP_KERNEL); GFP_KERNEL);
if (!control_phy) { if (!control_phy)
dev_err(&pdev->dev, "unable to alloc memory for control phy\n");
return -ENOMEM; return -ENOMEM;
}
control_phy->dev = &pdev->dev; control_phy->dev = &pdev->dev;
control_phy->type = *(enum omap_control_phy_type *)of_id->data; control_phy->type = *(enum omap_control_phy_type *)of_id->data;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment