From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5161809905987019698==" MIME-Version: 1.0 From: kbuild test robot To: kbuild-all@lists.01.org Subject: [chrome-os:chromeos-5.4 34/43] drivers/media/virtio/virtio_video_caps.c:298:5-11: ERROR: allocation function on line 297 returns NULL not ERR_PTR on failure Date: Thu, 19 Mar 2020 04:19:17 +0800 Message-ID: <202003190410.HPD6ohXD%lkp@intel.com> List-Id: --===============5161809905987019698== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chr= omeos-5.4 head: 4ab03425ee573fd6b97746d319f2c88b465a1534 commit: bbca48582a7342c1201691ce0eb08f1538376538 [34/43] BACKPORT: FROMLIST= : virtio_video: Add the Virtio Video V4L2 driver If you fix the issue, kindly add following tag Reported-by: kbuild test robot coccinelle warnings: (new ones prefixed by >>) >> drivers/media/virtio/virtio_video_caps.c:298:5-11: ERROR: allocation fun= ction on line 297 returns NULL not ERR_PTR on failure drivers/media/virtio/virtio_video_caps.c:380:5-11: ERROR: allocation fun= ction on line 379 returns NULL not ERR_PTR on failure -- >> drivers/media/virtio/virtio_video_driver.c:103:5-11: ERROR: allocation f= unction on line 102 returns NULL not ERR_PTR on failure -- >> drivers/media/virtio/virtio_video_vq.c:92:8-24: WARNING: kmem_cache_zall= oc should be used for vbuf, instead of kmem_cache_alloc/memset Please review and possibly fold the followup patch. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org --===============5161809905987019698==--