From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC] virtio: wrap config->reset calls
Date: Thu, 14 Oct 2021 01:15:59 +0800 [thread overview]
Message-ID: <202110140141.ivKNoePt-lkp@intel.com> (raw)
In-Reply-To: <20211013105226.20225-1-mst@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]
Hi "Michael,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on axboe-block/for-next]
[also build test ERROR on linus/master v5.15-rc5 next-20211013]
[cannot apply to char-misc/char-misc-testing linux/master rw-uml/linux-next bluetooth-next/master herbert-cryptodev-2.6/master herbert-crypto-2.6/master bluetooth/master linusw-gpio/for-next]
[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/Michael-S-Tsirkin/virtio-wrap-config-reset-calls/20211013-185724
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
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
# https://github.com/0day-ci/linux/commit/161cce1f8fc4812f5ce58f9c9a6815bd95594259
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Michael-S-Tsirkin/virtio-wrap-config-reset-calls/20211013-185724
git checkout 161cce1f8fc4812f5ce58f9c9a6815bd95594259
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/
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/virtio/virtio.c:207:13: error: static declaration of 'virtio_reset_device' follows non-static declaration
207 | static void virtio_reset_device(struct virtio_device *dev)
| ^~~~~~~~~~~~~~~~~~~
In file included from drivers/virtio/virtio.c:2:
include/linux/virtio.h:141:6: note: previous declaration of 'virtio_reset_device' with type 'void(struct virtio_device *)'
141 | void virtio_reset_device(struct virtio_device *dev);
| ^~~~~~~~~~~~~~~~~~~
>> drivers/virtio/virtio.c:207:13: error: 'virtio_reset_device' defined but not used [-Werror=unused-function]
207 | static void virtio_reset_device(struct virtio_device *dev)
| ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/virtio_reset_device +207 drivers/virtio/virtio.c
206
> 207 static void virtio_reset_device(struct virtio_device *dev)
208 {
209 dev->config->reset(dev);
210 }
211
---
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: 72457 bytes --]
next prev parent reply other threads:[~2021-10-13 17:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 10:55 [PATCH RFC] virtio: wrap config->reset calls Michael S. Tsirkin
2021-10-13 10:55 ` Michael S. Tsirkin
2021-10-13 10:55 ` Michael S. Tsirkin
2021-10-13 10:55 ` Michael S. Tsirkin
2021-10-13 11:00 ` Viresh Kumar
2021-10-13 11:00 ` Viresh Kumar
2021-10-13 11:00 ` Viresh Kumar
2021-10-13 11:00 ` Viresh Kumar
2021-10-13 11:03 ` David Hildenbrand
2021-10-13 11:03 ` David Hildenbrand
2021-10-13 11:03 ` David Hildenbrand
2021-10-13 11:03 ` David Hildenbrand
2021-10-13 12:17 ` Michael S. Tsirkin
2021-10-13 12:17 ` Michael S. Tsirkin
2021-10-13 12:17 ` Michael S. Tsirkin
2021-10-13 12:17 ` Michael S. Tsirkin
2021-10-13 16:00 ` David Hildenbrand
2021-10-13 16:00 ` David Hildenbrand
2021-10-13 16:00 ` David Hildenbrand
2021-10-13 16:00 ` David Hildenbrand
2021-10-13 13:16 ` Vivek Goyal
2021-10-13 13:16 ` Vivek Goyal
2021-10-13 13:16 ` Vivek Goyal
2021-10-13 13:16 ` Vivek Goyal
2021-10-13 15:46 ` Mathieu Poirier
2021-10-13 15:46 ` Mathieu Poirier
2021-10-13 15:46 ` Mathieu Poirier
2021-10-13 15:46 ` Mathieu Poirier
2021-10-13 16:18 ` Cristian Marussi
2021-10-13 16:18 ` Cristian Marussi
2021-10-13 16:18 ` Cristian Marussi
2021-10-13 16:18 ` Cristian Marussi
2021-10-13 16:26 ` Pankaj Gupta
2021-10-13 16:26 ` Pankaj Gupta
2021-10-13 16:26 ` Pankaj Gupta
2021-10-13 16:26 ` Pankaj Gupta
2021-10-13 17:15 ` kernel test robot [this message]
2021-10-14 6:11 ` Anton Yakovlev
2021-10-14 6:11 ` Anton Yakovlev
2021-10-14 6:11 ` Anton Yakovlev
2021-10-14 6:11 ` Anton Yakovlev
2021-10-14 8:36 ` Jean-Philippe Brucker
2021-10-14 8:36 ` Jean-Philippe Brucker
2021-10-14 8:36 ` Jean-Philippe Brucker
2021-10-14 8:36 ` Jean-Philippe Brucker
2021-10-14 8:36 ` Jean-Philippe Brucker
2021-10-17 14:12 ` Wolfram Sang
2021-10-17 14:12 ` Wolfram Sang
2021-10-17 14:12 ` Wolfram Sang
2021-10-17 14:12 ` Wolfram Sang
2021-10-18 9:11 ` Stefan Hajnoczi
2021-10-18 9:11 ` Stefan Hajnoczi
2021-10-18 9:11 ` Stefan Hajnoczi
2021-10-18 9:11 ` Stefan Hajnoczi
2021-10-18 9:11 ` Stefan Hajnoczi
2021-10-18 9:24 ` Stefano Garzarella
2021-10-18 9:24 ` Stefano Garzarella
2021-10-18 9:24 ` Stefano Garzarella
2021-10-18 9:24 ` Stefano Garzarella
2021-10-18 9:24 ` Stefano Garzarella
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=202110140141.ivKNoePt-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.