misc: lis3lv02d: Do not log an error when kmalloc fails

Logging an error when kmalloc fails is not necessary (and in general
should be avoided) because the malloc failure will already complain
loudly itself.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20210217102501.31758-3-hdegoede@redhat.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/misc/lis3lv02d/lis3lv02d.c b/drivers/misc/lis3lv02d/lis3lv02d.c
index 22dacfaad02fbc0d31b2d2fce05b8cd0cab95aea..70c5bb1e6f4966058be0dd133dcf6b5047185516 100644 (file)
--- a/drivers/misc/lis3lv02d/lis3lv02d.c
+++ b/drivers/misc/lis3lv02d/lis3lv02d.c
@@ -1179,10 +1179,8 @@ int lis3lv02d_init_device(struct lis3lv02d *lis3)
        lis3->reg_cache = kzalloc(max(sizeof(lis3_wai8_regs),
                                     sizeof(lis3_wai12_regs)), GFP_KERNEL);
 
-       if (lis3->reg_cache == NULL) {
-               printk(KERN_ERR DRIVER_NAME "out of memory\n");
+       if (lis3->reg_cache == NULL)
                return -ENOMEM;
-       }
 
        mutex_init(&lis3->mutex);
        atomic_set(&lis3->wake_thread, 0);