From: Hans Verkuil <hans.verk...@cisco.com>

There is nothing wrong with using an unknown buffer type. So
stop spamming the kernel log whenever this happens. The kernel
will just return -EINVAL to signal this.

Signed-off-by: Hans Verkuil <hans.verk...@cisco.com>
---
 drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/media/v4l2-core/v4l2-compat-ioctl32.c 
b/drivers/media/v4l2-core/v4l2-compat-ioctl32.c
index 6e3fbbde2c9c..790473b45a21 100644
--- a/drivers/media/v4l2-core/v4l2-compat-ioctl32.c
+++ b/drivers/media/v4l2-core/v4l2-compat-ioctl32.c
@@ -178,8 +178,6 @@ static int __get_v4l2_format32(struct v4l2_format *kp, 
struct v4l2_format32 __us
                return copy_from_user(&kp->fmt.meta, &up->fmt.meta,
                                      sizeof(kp->fmt.meta)) ? -EFAULT : 0;
        default:
-               pr_info("compat_ioctl32: unexpected VIDIOC_FMT type %d\n",
-                       kp->type);
                return -EINVAL;
        }
 }
@@ -232,8 +230,6 @@ static int __put_v4l2_format32(struct v4l2_format *kp, 
struct v4l2_format32 __us
                return copy_to_user(&up->fmt.meta, &kp->fmt.meta,
                                    sizeof(kp->fmt.meta)) ?  -EFAULT : 0;
        default:
-               pr_info("compat_ioctl32: unexpected VIDIOC_FMT type %d\n",
-                       kp->type);
                return -EINVAL;
        }
 }
-- 
2.15.1

Reply via email to