All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: clean up i915_drv.h, part 1
Date: Fri, 07 Jan 2022 13:29:33 -0000	[thread overview]
Message-ID: <164156217301.24389.16704081546728759116@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1641561552.git.jani.nikula@intel.com>

== Series Details ==

Series: drm/i915: clean up i915_drv.h, part 1
URL   : https://patchwork.freedesktop.org/series/98608/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
60e75eead03f drm/i915: split out i915_getparam.h from i915_drv.h
-:51: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#51: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 46 lines checked
a0d78c938f8c drm/i915: split out i915_cmd_parser.h from i915_drv.h
-:50: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#50: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 74 lines checked
b440d4c86973 drm/i915: split out i915_gem_evict.h from i915_drv.h
-:72: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#72: 
new file mode 100644

-:94: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#94: FILE: drivers/gpu/drm/i915/i915_gem_evict.h:18:
+					  unsigned flags);

total: 0 errors, 2 warnings, 0 checks, 76 lines checked
31027a97d644 drm/i915: split out gem/i915_gem_userptr.h from i915_drv.h
-:24: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#24: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 36 lines checked
d12e93546327 drm/i915: split out gem/i915_gem_tiling.h from i915_drv.h
-:24: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#24: 
new file mode 100644

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



  parent reply	other threads:[~2022-01-07 13:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 13:20 [Intel-gfx] [PATCH 0/5] drm/i915: clean up i915_drv.h, part 1 Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 1/5] drm/i915: split out i915_getparam.h from i915_drv.h Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 2/5] drm/i915: split out i915_cmd_parser.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 3/5] drm/i915: split out i915_gem_evict.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 4/5] drm/i915: split out gem/i915_gem_userptr.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 5/5] drm/i915: split out gem/i915_gem_tiling.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 1/5] drm/i915: split out i915_getparam.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 2/5] drm/i915: split out i915_cmd_parser.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 3/5] drm/i915: split out i915_gem_evict.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 4/5] drm/i915: split out gem/i915_gem_userptr.h " Jani Nikula
2022-01-07 13:20 ` [Intel-gfx] [PATCH 5/5] drm/i915: split out gem/i915_gem_tiling.h " Jani Nikula
2022-01-07 13:25 ` [Intel-gfx] [PATCH 0/5] drm/i915: clean up i915_drv.h, part 1 Jani Nikula
2022-01-10 14:25   ` Jani Nikula
2022-01-07 13:29 ` Patchwork [this message]
2022-01-07 13:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-01-07 13:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-07 18:18 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=164156217301.24389.16704081546728759116@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.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.