From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v4 1/3] virtio: add dma-buf support for exported objects
Date: Mon, 01 Jun 2020 03:07:11 +0800 [thread overview]
Message-ID: <202006010301.TMQFzLST%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2599 bytes --]
In-Reply-To: <20200526105811.30784-2-stevensd@chromium.org>
References: <20200526105811.30784-2-stevensd@chromium.org>
TO: David Stevens <stevensd@chromium.org>
TO: Gerd Hoffmann <kraxel@redhat.com>
TO: David Airlie <airlied@linux.ie>
TO: Daniel Vetter <daniel@ffwll.ch>
TO: Sumit Semwal <sumit.semwal@linaro.org>
CC: "Michael S . Tsirkin" <mst@redhat.com>
CC: Jason Wang <jasowang@redhat.com>
CC: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
CC: Maxime Ripard <mripard@kernel.org>
CC: Thomas Zimmermann <tzimmermann@suse.de>
CC: David Stevens <stevensd@chromium.org>
Hi David,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20200525]
[also build test WARNING on v5.7-rc7]
[cannot apply to linus/master v5.7-rc7 v5.7-rc6 v5.7-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/David-Stevens/Support-virtio-cross-device-resources/20200526-190644
base: 7b4cb0a48db03a67d1ce21c4f97b1508a241a2e7
config: x86_64-randconfig-a002-20200531 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5)
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 x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/virtio/virtio_dma_buf.o: warning: objtool: __llvm_gcov_writeout()+0x0: call without frame pointer save/setup
>> drivers/virtio/virtio_dma_buf.o: warning: objtool: __llvm_gcov_reset()+0x0: call without frame pointer save/setup
>> drivers/virtio/virtio_dma_buf.o: warning: objtool: __llvm_gcov_flush()+0x0: call without frame pointer save/setup
>> drivers/virtio/virtio_dma_buf.o: warning: objtool: __llvm_gcov_init()+0x0: call without frame pointer save/setup
---
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: 32603 bytes --]
next reply other threads:[~2020-05-31 19:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 19:07 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-26 10:58 [virtio-dev] [PATCH v4 0/3] Support virtio cross-device resources David Stevens
2020-05-26 10:58 ` [PATCH v4 1/3] virtio: add dma-buf support for exported objects David Stevens
2020-05-26 10:58 ` David Stevens
2020-06-04 19:05 ` Michael S. Tsirkin
2020-06-04 19:05 ` Michael S. Tsirkin
2020-06-05 1:28 ` David Stevens
2020-06-05 1:28 ` David Stevens
2020-06-06 20:04 ` Michael S. Tsirkin
2020-06-06 20:04 ` Michael S. Tsirkin
2020-06-08 1:33 ` David Stevens
2020-06-08 1:33 ` David Stevens
2020-06-08 6:00 ` Michael S. Tsirkin
2020-06-08 6:00 ` Michael S. Tsirkin
2020-06-08 8:32 ` David Stevens
2020-06-08 8:32 ` David Stevens
2020-06-08 9:05 ` Michael S. Tsirkin
2020-06-08 9:05 ` Michael S. Tsirkin
2020-06-08 9:30 ` David Stevens
2020-06-08 9:30 ` David Stevens
2020-06-18 12:28 ` Guennadi Liakhovetski
2020-06-18 12:28 ` Guennadi Liakhovetski
2020-06-18 12:28 ` Guennadi Liakhovetski
2020-06-19 1:57 ` David Stevens
2020-06-19 1:57 ` David Stevens
2020-06-19 6:53 ` Guennadi Liakhovetski
2020-06-19 6:53 ` Guennadi Liakhovetski
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=202006010301.TMQFzLST%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.