From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kraxel:drm-virtio-buffers 3/3] drivers/gpu/drm/virtio/virtio-buffers.c:48:21: sparse: sparse: restricted __le32 degrades to integer
Date: Sun, 19 Jan 2020 08:12:12 +0800 [thread overview]
Message-ID: <202001190846.tUgdhmjs%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
tree: git://git.kraxel.org/linux drm-virtio-buffers
head: 45c447e91f0c14344e0552dd72a65201673ff19b
commit: 45c447e91f0c14344e0552dd72a65201673ff19b [3/3] [wip] virtio-buffers: guest driver
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-131-g22978b6b-dirty
git checkout 45c447e91f0c14344e0552dd72a65201673ff19b
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/virtio/virtio-buffers.c:48:21: sparse: sparse: restricted __le32 degrades to integer
>> drivers/gpu/drm/virtio/virtio-buffers.c:41:6: sparse: sparse: symbol 'virtbufs_ctrl_ack' was not declared. Should it be static?
Please review and possibly fold the followup patch.
vim +48 drivers/gpu/drm/virtio/virtio-buffers.c
40
> 41 void virtbufs_ctrl_ack(struct virtqueue *vq)
42 {
43 // struct virtbufs_device *vb = vq->vdev->priv;
44 struct virtbufs_request *req;
45 int length;
46
47 req = virtqueue_get_buf(vq, &length);
> 48 if (req->rsp.response != VIRTIO_BUFFERS_RSP_OK)
49 DRM_ERROR("command 0x%04x -> error 0x%4x\n",
50 req->cmd.command, req->rsp.response);
51 kfree(req);
52 }
53
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
next reply other threads:[~2020-01-19 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 0:12 kbuild test robot [this message]
2020-01-19 0:12 ` [RFC PATCH kraxel] [wip] virtio-buffers: virtbufs_ctrl_ack() can be static kbuild test robot
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=202001190846.tUgdhmjs%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.