alloc failures already get standardized OOM
messages and a dump_stack.

Signed-off-by: Joe Perches <j...@perches.com>
---
 drivers/net/caif/caif_shmcore.c | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/drivers/net/caif/caif_shmcore.c b/drivers/net/caif/caif_shmcore.c
index bc497d7..bce8bac 100644
--- a/drivers/net/caif/caif_shmcore.c
+++ b/drivers/net/caif/caif_shmcore.c
@@ -633,9 +633,6 @@ int caif_shmcore_probe(struct shmdev_layer *pshm_dev)
                                kmalloc(sizeof(struct buf_list), GFP_KERNEL);
 
                if (tx_buf == NULL) {
-                       pr_warn("ERROR, Could not"
-                                       " allocate dynamic mem. for tx_buf,"
-                                       " Bailing out ...\n");
                        free_netdev(pshm_dev->pshm_netdev);
                        return -ENOMEM;
                }
@@ -662,9 +659,6 @@ int caif_shmcore_probe(struct shmdev_layer *pshm_dev)
                                kmalloc(sizeof(struct buf_list), GFP_KERNEL);
 
                if (rx_buf == NULL) {
-                       pr_warn("ERROR, Could not"
-                                       " allocate dynamic mem.for rx_buf,"
-                                       " Bailing out ...\n");
                        free_netdev(pshm_dev->pshm_netdev);
                        return -ENOMEM;
                }
-- 
1.8.0.dirty

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to