All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 18 Nov 2019 13:35:05 -0000	[thread overview]
Message-ID: <157408410594.2240.2784308451446609317@emeril.freedesktop.org> (raw)
In-Reply-To: <20191118105923.7991-1-jasowang@redhat.com>

== Series Details ==

Series: mdev based hardware virtio offloading support
URL   : https://patchwork.freedesktop.org/series/69621/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
67f3ea3cda70 mdev: make mdev bus agnostic
-:648: CHECK:LINE_SPACING: Please don't use multiple blank lines
#648: FILE: drivers/vfio/mdev/mdev_private.h:42:
+
+

-:651: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'bus' - possible side-effects?
#651: FILE: drivers/vfio/mdev/mdev_private.h:44:
+#define dev_is_mdev(d, bus)	((d)->bus == bus)

-:651: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'bus' may be better as '(bus)' to avoid precedence issues
#651: FILE: drivers/vfio/mdev/mdev_private.h:44:
+#define dev_is_mdev(d, bus)	((d)->bus == bus)

-:656: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#656: 
new file mode 100644

total: 0 errors, 1 warnings, 3 checks, 776 lines checked
f69d8d9902fd mdev: split out VFIO bus specific parent ops
-:285: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'mdev' - possible side-effects?
#285: FILE: drivers/vfio/mdev/mdev_vfio.c:20:
+#define to_vfio_mdev_device(mdev) container_of(mdev, \
+					       struct mdev_vfio_device, mdev)

total: 0 errors, 0 warnings, 1 checks, 585 lines checked
8544fcd816bc mdev: move to drivers/
-:57: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#57: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 92 lines checked
fe3f935905d1 mdev: introduce mediated virtio bus
-:57: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#57: 
new file mode 100644

-:91: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'mdev' - possible side-effects?
#91: FILE: drivers/mdev/virtio.c:30:
+#define to_mdev_virtio(mdev) container_of(mdev, \
+					  struct mdev_virtio_device, mdev)

-:405: CHECK:LINE_SPACING: Please don't use multiple blank lines
#405: FILE: scripts/mod/file2alias.c:1348:
+
+

total: 0 errors, 1 warnings, 2 checks, 361 lines checked
bbb2f0eac428 virtio: introduce a mdev based transport
-:52: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#52: 
new file mode 100644

-:111: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#111: FILE: drivers/virtio/virtio_mdev.c:55:
+static void virtio_mdev_get(struct virtio_device *vdev, unsigned offset,

-:112: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#112: FILE: drivers/virtio/virtio_mdev.c:56:
+			    void *buf, unsigned len)

-:120: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#120: FILE: drivers/virtio/virtio_mdev.c:64:
+static void virtio_mdev_set(struct virtio_device *vdev, unsigned offset,

-:121: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#121: FILE: drivers/virtio/virtio_mdev.c:65:
+			    const void *buf, unsigned len)

-:134: CHECK:LINE_SPACING: Please don't use multiple blank lines
#134: FILE: drivers/virtio/virtio_mdev.c:78:
+
+

-:302: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#302: FILE: drivers/virtio/virtio_mdev.c:246:
+static int virtio_mdev_find_vqs(struct virtio_device *vdev, unsigned nvqs,

total: 0 errors, 6 warnings, 1 checks, 443 lines checked
8a37245a6260 docs: sample driver to demonstrate how to implement virtio-mdev framework
-:62: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#62: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 717 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: Mon, 18 Nov 2019 13:35:05 -0000	[thread overview]
Message-ID: <157408410594.2240.2784308451446609317@emeril.freedesktop.org> (raw)
Message-ID: <20191118133505.QDFrkmScMHfpcy3wmreZqf5S5YAxnmHUJJmquF19Tq0@z> (raw)
In-Reply-To: <20191118105923.7991-1-jasowang@redhat.com>

== Series Details ==

Series: mdev based hardware virtio offloading support
URL   : https://patchwork.freedesktop.org/series/69621/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
67f3ea3cda70 mdev: make mdev bus agnostic
-:648: CHECK:LINE_SPACING: Please don't use multiple blank lines
#648: FILE: drivers/vfio/mdev/mdev_private.h:42:
+
+

-:651: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'bus' - possible side-effects?
#651: FILE: drivers/vfio/mdev/mdev_private.h:44:
+#define dev_is_mdev(d, bus)	((d)->bus == bus)

-:651: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'bus' may be better as '(bus)' to avoid precedence issues
#651: FILE: drivers/vfio/mdev/mdev_private.h:44:
+#define dev_is_mdev(d, bus)	((d)->bus == bus)

-:656: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#656: 
new file mode 100644

total: 0 errors, 1 warnings, 3 checks, 776 lines checked
f69d8d9902fd mdev: split out VFIO bus specific parent ops
-:285: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'mdev' - possible side-effects?
#285: FILE: drivers/vfio/mdev/mdev_vfio.c:20:
+#define to_vfio_mdev_device(mdev) container_of(mdev, \
+					       struct mdev_vfio_device, mdev)

total: 0 errors, 0 warnings, 1 checks, 585 lines checked
8544fcd816bc mdev: move to drivers/
-:57: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#57: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 92 lines checked
fe3f935905d1 mdev: introduce mediated virtio bus
-:57: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#57: 
new file mode 100644

-:91: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'mdev' - possible side-effects?
#91: FILE: drivers/mdev/virtio.c:30:
+#define to_mdev_virtio(mdev) container_of(mdev, \
+					  struct mdev_virtio_device, mdev)

-:405: CHECK:LINE_SPACING: Please don't use multiple blank lines
#405: FILE: scripts/mod/file2alias.c:1348:
+
+

total: 0 errors, 1 warnings, 2 checks, 361 lines checked
bbb2f0eac428 virtio: introduce a mdev based transport
-:52: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#52: 
new file mode 100644

-:111: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#111: FILE: drivers/virtio/virtio_mdev.c:55:
+static void virtio_mdev_get(struct virtio_device *vdev, unsigned offset,

-:112: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#112: FILE: drivers/virtio/virtio_mdev.c:56:
+			    void *buf, unsigned len)

-:120: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#120: FILE: drivers/virtio/virtio_mdev.c:64:
+static void virtio_mdev_set(struct virtio_device *vdev, unsigned offset,

-:121: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#121: FILE: drivers/virtio/virtio_mdev.c:65:
+			    const void *buf, unsigned len)

-:134: CHECK:LINE_SPACING: Please don't use multiple blank lines
#134: FILE: drivers/virtio/virtio_mdev.c:78:
+
+

-:302: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#302: FILE: drivers/virtio/virtio_mdev.c:246:
+static int virtio_mdev_find_vqs(struct virtio_device *vdev, unsigned nvqs,

total: 0 errors, 6 warnings, 1 checks, 443 lines checked
8a37245a6260 docs: sample driver to demonstrate how to implement virtio-mdev framework
-:62: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#62: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 717 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-11-18 13:35 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 10:59 [PATCH V13 0/6] mdev based hardware virtio offloading support Jason Wang
2019-11-18 10:59 ` [Intel-gfx] " Jason Wang
2019-11-18 10:59 ` Jason Wang
2019-11-18 10:59 ` [PATCH V13 1/6] mdev: make mdev bus agnostic Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-19  3:08   ` Randy Dunlap
2019-11-19  3:08     ` [Intel-gfx] " Randy Dunlap
2019-11-19  3:08     ` Randy Dunlap
2019-11-19  3:08     ` Randy Dunlap
2019-11-18 10:59 ` [PATCH V13 2/6] mdev: split out VFIO bus specific parent ops Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59 ` [PATCH V13 3/6] mdev: move to drivers/ Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-19  3:11   ` Randy Dunlap
2019-11-19  3:11     ` [Intel-gfx] " Randy Dunlap
2019-11-19  3:11     ` Randy Dunlap
2019-11-19  3:11     ` Randy Dunlap
2019-11-18 10:59 ` [PATCH V13 4/6] mdev: introduce mediated virtio bus Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 13:41   ` Jason Gunthorpe
2019-11-18 13:41     ` [Intel-gfx] " Jason Gunthorpe
2019-11-18 13:41     ` Jason Gunthorpe
2019-11-18 20:27     ` Michael S. Tsirkin
2019-11-18 20:27       ` [Intel-gfx] " Michael S. Tsirkin
2019-11-18 20:27       ` Michael S. Tsirkin
2019-11-18 20:28       ` Jason Gunthorpe
2019-11-18 20:28         ` [Intel-gfx] " Jason Gunthorpe
2019-11-18 20:28         ` Jason Gunthorpe
2019-11-19  2:41         ` Jason Wang
2019-11-19  2:41           ` [Intel-gfx] " Jason Wang
2019-11-19  2:41           ` Jason Wang
2019-11-19 12:38           ` Jason Gunthorpe
2019-11-19 12:38             ` [Intel-gfx] " Jason Gunthorpe
2019-11-19 14:02             ` Jason Wang
2019-11-19 14:02               ` [Intel-gfx] " Jason Wang
2019-11-19 14:02               ` Jason Wang
2019-11-19 14:14               ` Jason Gunthorpe
2019-11-19 14:14                 ` [Intel-gfx] " Jason Gunthorpe
2019-11-20  2:14                 ` Jason Wang
2019-11-20  2:14                   ` [Intel-gfx] " Jason Wang
2019-11-20  2:14                   ` Jason Wang
2019-11-20 13:49                   ` Jason Gunthorpe
2019-11-20 13:49                     ` [Intel-gfx] " Jason Gunthorpe
2019-11-20 13:49                     ` Jason Gunthorpe
2019-11-21  3:05                     ` Jason Wang
2019-11-21  3:05                       ` [Intel-gfx] " Jason Wang
2019-11-21  3:05                       ` Jason Wang
2019-11-26 12:07                   ` Rob Miller
2019-11-26 12:07                     ` [Intel-gfx] " Rob Miller
2019-11-26 12:07                     ` Rob Miller
2019-11-19  2:40     ` Jason Wang
2019-11-19  2:40       ` [Intel-gfx] " Jason Wang
2019-11-19  2:40       ` Jason Wang
2019-11-19  3:13   ` Randy Dunlap
2019-11-19  3:13     ` [Intel-gfx] " Randy Dunlap
2019-11-19  3:13     ` Randy Dunlap
2019-11-19  3:13     ` Randy Dunlap
2019-11-18 10:59 ` [PATCH V13 5/6] virtio: introduce a mdev based transport Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59 ` [PATCH V13 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang
2019-11-18 10:59   ` [Intel-gfx] " Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 10:59   ` Jason Wang
2019-11-18 15:17   ` Greg KH
2019-11-18 15:17     ` [Intel-gfx] " Greg KH
2019-11-18 15:17     ` Greg KH
2019-11-18 15:17     ` Greg KH
2019-11-19  3:03     ` Jason Wang
2019-11-19  3:03       ` [Intel-gfx] " Jason Wang
2019-11-19  3:03       ` Jason Wang
2019-11-19  3:03       ` Jason Wang
2019-11-19 12:40       ` Jason Gunthorpe
2019-11-19 12:40         ` [Intel-gfx] " Jason Gunthorpe
2019-11-19 14:07         ` Jason Wang
2019-11-19 14:07           ` [Intel-gfx] " Jason Wang
2019-11-19 14:07           ` Jason Wang
2019-11-19 16:39           ` Jason Gunthorpe
2019-11-19 16:39             ` [Intel-gfx] " Jason Gunthorpe
2019-11-18 15:45   ` Cornelia Huck
2019-11-18 15:45     ` [Intel-gfx] " Cornelia Huck
2019-11-18 15:45     ` Cornelia Huck
2019-11-18 15:45     ` Cornelia Huck
2019-11-19  3:04     ` Jason Wang
2019-11-19  3:04       ` [Intel-gfx] " Jason Wang
2019-11-19  3:04       ` Jason Wang
2019-11-19  3:04       ` Jason Wang
2019-11-18 13:35 ` Patchwork [this message]
2019-11-18 13:35   ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for mdev based hardware virtio offloading support Patchwork
2019-11-18 13:51 ` ✗ Fi.CI.DOCS: " Patchwork
2019-11-18 13:51   ` [Intel-gfx] " Patchwork
2019-11-18 14:25 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-11-18 14:25   ` [Intel-gfx] " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-11-07 15:11 [PATCH V11 0/6] " Jason Wang
2019-11-07 18:31 ` ✗ 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=157408410594.2240.2784308451446609317@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: 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.