From: kernel test robot <lkp@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: [vhost:vhost 38/45] include/linux/vdpa.h:43:28: sparse: sparse: expected ; at end of declaration
Date: Tue, 28 Jul 2020 22:23:22 +0800 [thread overview]
Message-ID: <20200728142322.GA9367@xsang-OptiPlex-9020> (raw)
[-- Attachment #1: Type: text/plain, Size: 3495 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
head: 84d40e4b4bc64456abf5ef5663871053b40e84ac
commit: fee8fe6bd8ccacd27e963b71b4f943be3721779e [38/45] vdpa: make sure set_features in invoked for legacy
:::::: branch date: 5 hours ago
:::::: commit date: 6 hours ago
config: x86_64-randconfig-s021-20200727 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-94-geb6779f6-dirty
git checkout fee8fe6bd8ccacd27e963b71b4f943be3721779e
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/vdpa/vdpa.c: note: in included file:
>> include/linux/vdpa.h:43:28: sparse: sparse: expected ; at end of declaration
include/linux/vdpa.h:43:28: sparse: sparse: Expected } at end of struct-union-enum-specifier
include/linux/vdpa.h:43:28: sparse: sparse: got .
--
drivers/vdpa/ifcvf/ifcvf_main.c: note: in included file (through drivers/vdpa/ifcvf/ifcvf_base.h):
>> include/linux/vdpa.h:43:28: sparse: sparse: expected ; at end of declaration
include/linux/vdpa.h:43:28: sparse: sparse: Expected } at end of struct-union-enum-specifier
include/linux/vdpa.h:43:28: sparse: sparse: got .
--
drivers/vdpa/ifcvf/ifcvf_base.c: note: in included file (through drivers/vdpa/ifcvf/ifcvf_base.h):
>> include/linux/vdpa.h:43:28: sparse: sparse: expected ; at end of declaration
include/linux/vdpa.h:43:28: sparse: sparse: Expected } at end of struct-union-enum-specifier
include/linux/vdpa.h:43:28: sparse: sparse: got .
# https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?id=fee8fe6bd8ccacd27e963b71b4f943be3721779e
git remote add vhost https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
git remote update vhost
git checkout fee8fe6bd8ccacd27e963b71b4f943be3721779e
vim +43 include/linux/vdpa.h
c25a26e653a61b Jason Wang 2020-05-29 29
961e9c84077f6c Jason Wang 2020-03-26 30 /**
961e9c84077f6c Jason Wang 2020-03-26 31 * vDPA device - representation of a vDPA device
961e9c84077f6c Jason Wang 2020-03-26 32 * @dev: underlying device
961e9c84077f6c Jason Wang 2020-03-26 33 * @dma_dev: the actual device that is performing DMA
961e9c84077f6c Jason Wang 2020-03-26 34 * @config: the configuration ops for this device.
961e9c84077f6c Jason Wang 2020-03-26 35 * @index: device index
fee8fe6bd8ccac Michael S. Tsirkin 2020-07-27 36 * @features_valid: were features initialized? for legacy guests
961e9c84077f6c Jason Wang 2020-03-26 37 */
961e9c84077f6c Jason Wang 2020-03-26 38 struct vdpa_device {
961e9c84077f6c Jason Wang 2020-03-26 39 struct device dev;
961e9c84077f6c Jason Wang 2020-03-26 40 struct device *dma_dev;
961e9c84077f6c Jason Wang 2020-03-26 41 const struct vdpa_config_ops *config;
961e9c84077f6c Jason Wang 2020-03-26 42 unsigned int index;
fee8fe6bd8ccac Michael S. Tsirkin 2020-07-27 @43 bool features_valid.
961e9c84077f6c Jason Wang 2020-03-26 44 };
961e9c84077f6c Jason Wang 2020-03-26 45
---
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: 32341 bytes --]
reply other threads:[~2020-07-28 14:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200728142322.GA9367@xsang-OptiPlex-9020 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox