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 Remove some hacks required for GuC 62.0.0 (rev2)
Date: Thu, 13 Jan 2022 19:17:36 -0000	[thread overview]
Message-ID: <164210145658.19001.4981556650007477015@emeril.freedesktop.org> (raw)
In-Reply-To: <20220113181351.21296-1-matthew.brost@intel.com>

== Series Details ==

Series: Remove some hacks required for GuC 62.0.0 (rev2)
URL   : https://patchwork.freedesktop.org/series/98773/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
0bbf21e5b612 drm/i915/selftests: Add a cancel request selftest that triggers a reset
6c1f06c0b615 drm/i915/guc: Remove hacks for reset and schedule disable G2H being received out of order
-:14: WARNING:TYPO_SPELLING: 'cancelation' may be misspelled - perhaps 'cancellation'?
#14: 
  - s/cancelation/cancellation
      ^^^^^^^^^^^

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



  parent reply	other threads:[~2022-01-13 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 18:13 [PATCH 0/2] Remove some hacks required for GuC 62.0.0 Matthew Brost
2022-01-13 18:13 ` [Intel-gfx] " Matthew Brost
2022-01-13 18:13 ` [PATCH 1/2] drm/i915/selftests: Add a cancel request selftest that triggers a reset Matthew Brost
2022-01-13 18:13   ` [Intel-gfx] " Matthew Brost
2022-01-13 18:37   ` John Harrison
2022-01-13 18:37     ` [Intel-gfx] " John Harrison
2022-01-13 18:13 ` [PATCH 2/2] drm/i915/guc: Remove hacks for reset and schedule disable G2H being received out of order Matthew Brost
2022-01-13 18:13   ` [Intel-gfx] " Matthew Brost
2022-01-13 19:17 ` Patchwork [this message]
2022-01-13 19:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Remove some hacks required for GuC 62.0.0 (rev2) Patchwork
2022-01-13 20:53 ` [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=164210145658.19001.4981556650007477015@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.