All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for CT changes required for GuC submission (rev2)
Date: Thu, 01 Jul 2021 23:20:18 -0000	[thread overview]
Message-ID: <162518161896.15053.13689223281310080568@emeril.freedesktop.org> (raw)
In-Reply-To: <20210701171550.49353-1-matthew.brost@intel.com>

== Series Details ==

Series: CT changes required for GuC submission (rev2)
URL   : https://patchwork.freedesktop.org/series/91943/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
1bcca481ebc1 drm/i915/guc: Relax CTB response timeout
ee04968a1998 drm/i915/guc: Improve error message for unsolicited CT response
8cab0a3b4751 drm/i915/guc: Increase size of CTB buffers
239769e0c636 drm/i915/guc: Add non blocking CTB send function
2668763f4f82 drm/i915/guc: Add stall timer to non blocking CTB send function
5e72f3dc91ad drm/i915/guc: Optimize CTB writes and reads
b25f638c19a5 drm/i915/guc: Module load failure test for CT buffer creation
-:38: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: John Harrison <John.C.Harrison@Intel.com>' != 'Signed-off-by: John Harrison <john.c.harrison@intel.com>'

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


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

  parent reply	other threads:[~2021-07-01 23:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 17:15 [PATCH 0/7] CT changes required for GuC submission Matthew Brost
2021-07-01 17:15 ` [Intel-gfx] " Matthew Brost
2021-07-01 17:15 ` [PATCH 1/7] drm/i915/guc: Relax CTB response timeout Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-01 17:15 ` [PATCH 2/7] drm/i915/guc: Improve error message for unsolicited CT response Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-01 17:15 ` [PATCH 3/7] drm/i915/guc: Increase size of CTB buffers Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-01 17:15 ` [PATCH 4/7] drm/i915/guc: Add non blocking CTB send function Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-06 18:12   ` John Harrison
2021-07-06 18:12     ` [Intel-gfx] " John Harrison
2021-07-06 18:17     ` Matthew Brost
2021-07-06 18:17       ` [Intel-gfx] " Matthew Brost
2021-07-01 17:15 ` [PATCH 5/7] drm/i915/guc: Add stall timer to " Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-06 18:27   ` John Harrison
2021-07-06 18:27     ` [Intel-gfx] " John Harrison
2021-07-01 17:15 ` [PATCH 6/7] drm/i915/guc: Optimize CTB writes and reads Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-06 19:00   ` John Harrison
2021-07-06 19:00     ` [Intel-gfx] " John Harrison
2021-07-06 19:12     ` Michal Wajdeczko
2021-07-06 19:12       ` [Intel-gfx] " Michal Wajdeczko
2021-07-06 19:19       ` John Harrison
2021-07-06 19:19         ` [Intel-gfx] " John Harrison
2021-07-06 19:33         ` Michal Wajdeczko
2021-07-06 19:33           ` [Intel-gfx] " Michal Wajdeczko
2021-07-06 21:22           ` Matthew Brost
2021-07-06 21:22             ` [Intel-gfx] " Matthew Brost
2021-07-06 22:41           ` John Harrison
2021-07-06 22:41             ` [Intel-gfx] " John Harrison
2021-07-01 17:15 ` [PATCH 7/7] drm/i915/guc: Module load failure test for CT buffer creation Matthew Brost
2021-07-01 17:15   ` [Intel-gfx] " Matthew Brost
2021-07-01 23:20 ` Patchwork [this message]
2021-07-01 23:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for CT changes required for GuC submission (rev2) Patchwork
2021-07-01 23:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-02  6:55 ` [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=162518161896.15053.13689223281310080568@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.brost@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.