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: ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/3] drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem()
Date: Fri, 04 Oct 2019 13:16:02 -0000	[thread overview]
Message-ID: <20191004131602.26993.54180@emeril.freedesktop.org> (raw)
In-Reply-To: <20191004122019.12009-1-jani.nikula@intel.com>

== Series Details ==

Series: series starting with [CI,1/3] drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem()
URL   : https://patchwork.freedesktop.org/series/67592/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
095e27e1a8ba drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem()
b8e3e32314d6 drm/i915: split out i915_switcheroo.[ch] from i915_drv.c
-:172: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#172: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 208 lines checked
cda2e2643fa7 drm/i915: move gmbus setup down to intel_modeset_init()

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

  parent reply	other threads:[~2019-10-04 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 12:20 [CI 1/3] drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem() Jani Nikula
2019-10-04 12:20 ` [CI 2/3] drm/i915: split out i915_switcheroo.[ch] from i915_drv.c Jani Nikula
2019-10-04 12:20 ` [CI 3/3] drm/i915: move gmbus setup down to intel_modeset_init() Jani Nikula
2019-10-04 13:16 ` Patchwork [this message]
2019-10-04 13:55 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/3] drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem() Patchwork
2019-10-04 21:19 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-10-06  8:46   ` Jani Nikula

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=20191004131602.26993.54180@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.