All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Akeem G Abodunrin" <akeem.g.abodunrin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Security mitigation for Intel Gen7/7.5 HWs
Date: Thu, 20 Feb 2020 03:08:37 -0000	[thread overview]
Message-ID: <158216811789.17407.8697767988269964476@emeril.freedesktop.org> (raw)
In-Reply-To: <20200219180256.15524-1-akeem.g.abodunrin@intel.com>

== Series Details ==

Series: Security mitigation for Intel Gen7/7.5 HWs
URL   : https://patchwork.freedesktop.org/series/73686/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
ffdac73cd979 drm/i915: Add mechanism to submit a context WA on ring submission
d66eb25865a2 drm/i915/gen7: Clear all EU/L3 residual contexts
-:41: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#41: 
new file mode 100644

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

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

  parent reply	other threads:[~2020-02-20  3:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 18:02 [PATCH v3 0/2] Security mitigation for Intel Gen7/7.5 HWs Akeem G Abodunrin
2020-02-19 18:02 ` [Intel-gfx] " Akeem G Abodunrin
2020-02-19 18:02 ` [PATCH v3 1/2] drm/i915: Add mechanism to submit a context WA on ring submission Akeem G Abodunrin
2020-02-19 18:02   ` [Intel-gfx] " Akeem G Abodunrin
2020-02-19 18:02 ` [PATCH v3 2/2] drm/i915/gen7: Clear all EU/L3 residual contexts Akeem G Abodunrin
2020-02-19 18:02   ` [Intel-gfx] " Akeem G Abodunrin
2020-02-20  3:08 ` Patchwork [this message]
2020-02-20  3:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Security mitigation for Intel Gen7/7.5 HWs Patchwork
2020-02-20  7:56   ` Chris Wilson
2020-02-22  5:20 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-02-20 23:00 [PATCH v4 0/2] " Akeem G Abodunrin
2020-02-21  7:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-02-20 22:57 [PATCH 0/2] " Akeem G Abodunrin
2020-02-21  6:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-02-18 16:21 [PATCH v2 0/2] " Akeem G Abodunrin
2020-02-19  5:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-01-30 16:57 [PATCH 0/2] " Akeem G Abodunrin
2020-01-31  2:33 ` [Intel-gfx] ✗ 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=158216811789.17407.8697767988269964476@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=akeem.g.abodunrin@intel.com \
    --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 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.