All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Update error capture code to avoid using the current vma state
Date: Mon, 29 Nov 2021 22:36:56 -0000	[thread overview]
Message-ID: <163822541616.16120.326265818067936871@emeril.freedesktop.org> (raw)
In-Reply-To: <20211129202245.472043-1-thomas.hellstrom@linux.intel.com>

== Series Details ==

Series: drm/i915: Update error capture code to avoid using the current vma state
URL   : https://patchwork.freedesktop.org/series/97385/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
1fc91c09d6c2 drm/i915: Update error capture code to avoid using the current vma state
-:796: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#796: 
new file mode 100644

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



  reply	other threads:[~2021-11-29 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 20:22 [PATCH v7] drm/i915: Update error capture code to avoid using the current vma state Thomas Hellström
2021-11-29 20:22 ` [Intel-gfx] " Thomas Hellström
2021-11-29 22:36 ` Patchwork [this message]
2021-11-29 22:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2021-11-29 23:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-30  1:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-30  5:45   ` Thomas Hellström
2021-11-30 16:30     ` Vudum, Lakshminarayana
2021-11-30 16:07 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-12-07 20:46 ` [Intel-gfx] [PATCH v7] " John Harrison
2021-12-07 20:54   ` Thomas Hellström

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=163822541616.16120.326265818067936871@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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.