Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Kill the undead i915_gem_batch_pool.c
Date: Thu, 22 Aug 2019 09:06:06 -0000	[thread overview]
Message-ID: <20190822090606.14427.29326@emeril.freedesktop.org> (raw)
In-Reply-To: <20190822065917.18988-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Kill the undead i915_gem_batch_pool.c
URL   : https://patchwork.freedesktop.org/series/65593/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
7db6eec8126c drm/i915: Kill the undead i915_gem_batch_pool.c
-:10: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 3f866026f0ce ("Merge drm/drm-next into drm-intel-next-queued")'
#10: 
References: 3f866026f0ce ("Merge drm/drm-next into drm-intel-next-queued")

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

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

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

  reply	other threads:[~2019-08-22  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22  6:59 [PATCH] drm/i915: Kill the undead i915_gem_batch_pool.c Chris Wilson
2019-08-22  9:06 ` Patchwork [this message]
2019-08-22  9:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-22 11:12 ` [PATCH] " Joonas Lahtinen
2019-08-22 11:17   ` Chris Wilson
2019-10-09 18:53     ` Sean Paul
2019-10-09 18:57       ` Chris Wilson
2019-10-09 19:12         ` Sean Paul
2019-08-23  2:15 ` ✓ Fi.CI.IGT: success 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=20190822090606.14427.29326@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox