From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] media: videobuf2: cleanup size argument from attach_dmabuf()
Date: Thu, 25 Mar 2021 11:44:32 +0800 [thread overview]
Message-ID: <202103251119.VjsULkdF-lkp@intel.com> (raw)
In-Reply-To: <20210325001712.197837-2-helen.koike@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 3200 bytes --]
Hi Helen,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on next-20210324]
[cannot apply to v5.12-rc4]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Helen-Koike/media-videobuf2-use-dmabuf-size-for-length/20210325-082047
base: git://linuxtv.org/media_tree.git master
config: powerpc64-randconfig-r016-20210325 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 5d6b4aa80d6df62b924a12af030c5ded868ee4f1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install powerpc64 cross compiling tool for clang build
# apt-get install binutils-powerpc64-linux-gnu
# https://github.com/0day-ci/linux/commit/41e2cea31db8378b33e31785aec668a009d1355b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Helen-Koike/media-videobuf2-use-dmabuf-size-for-length/20210325-082047
git checkout 41e2cea31db8378b33e31785aec668a009d1355b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/media/common/videobuf2/videobuf2-dma-sg.c:631:14: error: use of undeclared identifier 'dmabuf'; did you mean 'dbuf'?
buf->size = dmabuf->size;
^~~~~~
dbuf
drivers/media/common/videobuf2/videobuf2-dma-sg.c:608:75: note: 'dbuf' declared here
static void *vb2_dma_sg_attach_dmabuf(struct device *dev, struct dma_buf *dbuf,
^
1 error generated.
vim +631 drivers/media/common/videobuf2/videobuf2-dma-sg.c
607
608 static void *vb2_dma_sg_attach_dmabuf(struct device *dev, struct dma_buf *dbuf,
609 enum dma_data_direction dma_dir)
610 {
611 struct vb2_dma_sg_buf *buf;
612 struct dma_buf_attachment *dba;
613
614 if (WARN_ON(!dev))
615 return ERR_PTR(-EINVAL);
616
617 buf = kzalloc(sizeof(*buf), GFP_KERNEL);
618 if (!buf)
619 return ERR_PTR(-ENOMEM);
620
621 buf->dev = dev;
622 /* create attachment for the dmabuf with the user device */
623 dba = dma_buf_attach(dbuf, buf->dev);
624 if (IS_ERR(dba)) {
625 pr_err("failed to attach dmabuf\n");
626 kfree(buf);
627 return dba;
628 }
629
630 buf->dma_dir = dma_dir;
> 631 buf->size = dmabuf->size;
632 buf->db_attach = dba;
633
634 return buf;
635 }
636
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 40444 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Helen Koike <helen.koike@collabora.com>, linux-media@vger.kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
hverkuil@xs4all.nl, kernel@collabora.com,
linux-kernel@vger.kernel.org, jc@kynesim.co.uk,
laurent.pinchart@ideasonboard.com,
dave.stevenson@raspberrypi.org, tfiga@chromium.org,
Helen Koike <helen.koike@collabora.com>
Subject: Re: [PATCH 2/2] media: videobuf2: cleanup size argument from attach_dmabuf()
Date: Thu, 25 Mar 2021 11:44:32 +0800 [thread overview]
Message-ID: <202103251119.VjsULkdF-lkp@intel.com> (raw)
In-Reply-To: <20210325001712.197837-2-helen.koike@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 3120 bytes --]
Hi Helen,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on next-20210324]
[cannot apply to v5.12-rc4]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Helen-Koike/media-videobuf2-use-dmabuf-size-for-length/20210325-082047
base: git://linuxtv.org/media_tree.git master
config: powerpc64-randconfig-r016-20210325 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 5d6b4aa80d6df62b924a12af030c5ded868ee4f1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install powerpc64 cross compiling tool for clang build
# apt-get install binutils-powerpc64-linux-gnu
# https://github.com/0day-ci/linux/commit/41e2cea31db8378b33e31785aec668a009d1355b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Helen-Koike/media-videobuf2-use-dmabuf-size-for-length/20210325-082047
git checkout 41e2cea31db8378b33e31785aec668a009d1355b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/media/common/videobuf2/videobuf2-dma-sg.c:631:14: error: use of undeclared identifier 'dmabuf'; did you mean 'dbuf'?
buf->size = dmabuf->size;
^~~~~~
dbuf
drivers/media/common/videobuf2/videobuf2-dma-sg.c:608:75: note: 'dbuf' declared here
static void *vb2_dma_sg_attach_dmabuf(struct device *dev, struct dma_buf *dbuf,
^
1 error generated.
vim +631 drivers/media/common/videobuf2/videobuf2-dma-sg.c
607
608 static void *vb2_dma_sg_attach_dmabuf(struct device *dev, struct dma_buf *dbuf,
609 enum dma_data_direction dma_dir)
610 {
611 struct vb2_dma_sg_buf *buf;
612 struct dma_buf_attachment *dba;
613
614 if (WARN_ON(!dev))
615 return ERR_PTR(-EINVAL);
616
617 buf = kzalloc(sizeof(*buf), GFP_KERNEL);
618 if (!buf)
619 return ERR_PTR(-ENOMEM);
620
621 buf->dev = dev;
622 /* create attachment for the dmabuf with the user device */
623 dba = dma_buf_attach(dbuf, buf->dev);
624 if (IS_ERR(dba)) {
625 pr_err("failed to attach dmabuf\n");
626 kfree(buf);
627 return dba;
628 }
629
630 buf->dma_dir = dma_dir;
> 631 buf->size = dmabuf->size;
632 buf->db_attach = dba;
633
634 return buf;
635 }
636
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40444 bytes --]
next prev parent reply other threads:[~2021-03-25 3:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 0:17 [PATCH 1/2] media: videobuf2: use dmabuf size for length Helen Koike
2021-03-25 0:17 ` [PATCH 2/2] media: videobuf2: cleanup size argument from attach_dmabuf() Helen Koike
2021-03-25 3:44 ` kernel test robot [this message]
2021-03-25 3:44 ` kernel test robot
2021-03-25 10:20 ` [PATCH 1/2] media: videobuf2: use dmabuf size for length John Cox
2021-03-26 12:22 ` Helen Koike
2021-03-26 13:03 ` John Cox
2021-03-26 14:44 ` Helen Koike
2021-03-26 15:22 ` John Cox
2021-03-25 10:53 ` Laurent Pinchart
2021-03-26 12:29 ` Helen Koike
2022-01-28 10:23 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202103251119.VjsULkdF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.