From: Patchwork <patchwork@emeril.freedesktop.org> To: Jason Wang <jasowang@redhat.com> Cc: intel-gfx@lists.freedesktop.org Subject: ✗ Fi.CI.CHECKPATCH: warning for mdev based hardware virtio offloading support Date: Thu, 07 Nov 2019 18:31:11 -0000 [thread overview] Message-ID: <157315147194.21751.14768546797249469582@emeril.freedesktop.org> (raw) In-Reply-To: <20191107151109.23261-1-jasowang@redhat.com> == Series Details == Series: mdev based hardware virtio offloading support URL : https://patchwork.freedesktop.org/series/69135/ State : warning == Summary == $ dim checkpatch origin/drm-tip 9507b5357d7b mdev: class id support 58af09c8da00 modpost: add support for mdev class id e94f948040f5 mdev: introduce device specific ops -:500: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #500: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 618 lines checked 1643d29b8cd6 mdev: introduce virtio device and its device ops -:108: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #108: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 219 lines checked 9f42a0ac8dab virtio: introduce a mdev based transport -:53: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #53: new file mode 100644 -:113: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #113: FILE: drivers/virtio/virtio_mdev.c:56: +static void virtio_mdev_get(struct virtio_device *vdev, unsigned offset, -:114: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #114: FILE: drivers/virtio/virtio_mdev.c:57: + void *buf, unsigned len) -:122: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #122: FILE: drivers/virtio/virtio_mdev.c:65: +static void virtio_mdev_set(struct virtio_device *vdev, unsigned offset, -:123: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #123: FILE: drivers/virtio/virtio_mdev.c:66: + const void *buf, unsigned len) -:303: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #303: FILE: drivers/virtio/virtio_mdev.c:246: +static int virtio_mdev_find_vqs(struct virtio_device *vdev, unsigned nvqs, total: 0 errors, 6 warnings, 0 checks, 429 lines checked 202515ad0a81 docs: sample driver to demonstrate how to implement virtio-mdev framework -:63: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #63: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 714 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org> To: "Jason Wang" <jasowang@redhat.com> Cc: intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for mdev based hardware virtio offloading support Date: Thu, 07 Nov 2019 18:31:11 -0000 [thread overview] Message-ID: <157315147194.21751.14768546797249469582@emeril.freedesktop.org> (raw) Message-ID: <20191107183111.pDkApt72LL3G51beCDlwCuxAIj2JHRfmsUz74d3IZdg@z> (raw) In-Reply-To: <20191107151109.23261-1-jasowang@redhat.com> == Series Details == Series: mdev based hardware virtio offloading support URL : https://patchwork.freedesktop.org/series/69135/ State : warning == Summary == $ dim checkpatch origin/drm-tip 9507b5357d7b mdev: class id support 58af09c8da00 modpost: add support for mdev class id e94f948040f5 mdev: introduce device specific ops -:500: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #500: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 618 lines checked 1643d29b8cd6 mdev: introduce virtio device and its device ops -:108: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #108: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 219 lines checked 9f42a0ac8dab virtio: introduce a mdev based transport -:53: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #53: new file mode 100644 -:113: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #113: FILE: drivers/virtio/virtio_mdev.c:56: +static void virtio_mdev_get(struct virtio_device *vdev, unsigned offset, -:114: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #114: FILE: drivers/virtio/virtio_mdev.c:57: + void *buf, unsigned len) -:122: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #122: FILE: drivers/virtio/virtio_mdev.c:65: +static void virtio_mdev_set(struct virtio_device *vdev, unsigned offset, -:123: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #123: FILE: drivers/virtio/virtio_mdev.c:66: + const void *buf, unsigned len) -:303: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' #303: FILE: drivers/virtio/virtio_mdev.c:246: +static int virtio_mdev_find_vqs(struct virtio_device *vdev, unsigned nvqs, total: 0 errors, 6 warnings, 0 checks, 429 lines checked 202515ad0a81 docs: sample driver to demonstrate how to implement virtio-mdev framework -:63: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #63: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 714 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-07 18:31 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-07 15:11 [PATCH V11 0/6] mdev based hardware virtio offloading support Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [PATCH V11 1/6] mdev: class id support Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 19:35 ` Kirti Wankhede 2019-11-07 19:35 ` [Intel-gfx] " Kirti Wankhede 2019-11-07 19:35 ` Kirti Wankhede 2019-11-07 19:35 ` Kirti Wankhede 2019-11-07 19:35 ` Kirti Wankhede 2019-11-07 15:11 ` [PATCH V11 2/6] modpost: add support for mdev class id Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 19:36 ` Kirti Wankhede 2019-11-07 19:36 ` [Intel-gfx] " Kirti Wankhede 2019-11-07 19:36 ` Kirti Wankhede 2019-11-07 19:36 ` Kirti Wankhede 2019-11-07 19:36 ` Kirti Wankhede 2019-11-07 15:11 ` [PATCH V11 3/6] mdev: introduce device specific ops Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:36 ` Cornelia Huck 2019-11-07 15:36 ` [Intel-gfx] " Cornelia Huck 2019-11-07 15:36 ` Cornelia Huck 2019-11-07 15:36 ` Cornelia Huck 2019-11-07 15:36 ` Cornelia Huck 2019-11-07 19:39 ` Kirti Wankhede 2019-11-07 19:39 ` [Intel-gfx] " Kirti Wankhede 2019-11-07 19:39 ` Kirti Wankhede 2019-11-07 19:39 ` Kirti Wankhede 2019-11-07 19:39 ` Kirti Wankhede 2019-11-07 15:11 ` [PATCH V11 4/6] mdev: introduce virtio device and its device ops Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 19:42 ` Kirti Wankhede 2019-11-07 19:42 ` [Intel-gfx] " Kirti Wankhede 2019-11-07 19:42 ` Kirti Wankhede 2019-11-07 19:42 ` Kirti Wankhede 2019-11-07 19:42 ` Kirti Wankhede 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [PATCH V11 5/6] virtio: introduce a mdev based transport Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [PATCH V11 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` [Intel-gfx] " Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:11 ` Jason Wang 2019-11-07 15:34 ` Cornelia Huck 2019-11-07 15:34 ` [Intel-gfx] " Cornelia Huck 2019-11-07 15:34 ` Cornelia Huck 2019-11-07 15:34 ` Cornelia Huck 2019-11-07 15:34 ` Cornelia Huck 2019-11-07 15:54 ` [PATCH V11 0/6] mdev based hardware virtio offloading support Michael S. Tsirkin 2019-11-07 15:54 ` Michael S. Tsirkin 2019-11-07 15:54 ` [Intel-gfx] " Michael S. Tsirkin 2019-11-07 15:54 ` Michael S. Tsirkin 2019-11-07 15:54 ` Michael S. Tsirkin 2019-11-07 18:31 ` Patchwork [this message] 2019-11-07 18:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-11-07 18:52 ` ✓ Fi.CI.BAT: success " Patchwork 2019-11-07 18:52 ` [Intel-gfx] " Patchwork 2019-11-09 0:07 ` ✓ Fi.CI.IGT: " Patchwork 2019-11-09 0:07 ` [Intel-gfx] " Patchwork -- strict thread matches above, loose matches on Subject: below -- 2019-11-18 10:59 [PATCH V13 0/6] " Jason Wang 2019-11-18 13:35 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-11-06 13:35 [PATCH V10 0/6] " Jason Wang 2019-11-06 16:30 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-11-06 7:05 [PATCH V9 0/6] " Jason Wang 2019-11-06 7:35 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-11-05 9:32 [PATCH V8 0/6] " Jason Wang 2019-11-05 10:26 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-09-20 8:20 [RFC PATCH V2 0/6] " Jason Wang 2019-09-20 12:10 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
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=157315147194.21751.14768546797249469582@emeril.freedesktop.org \ --to=patchwork@emeril.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jasowang@redhat.com \ /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: linkBe 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.