From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/2] drm/i915/uc: Update HuC firmware naming convention and load latest HuC
Date: Thu, 19 Sep 2019 22:35:30 -0000 [thread overview]
Message-ID: <20190919223530.23914.56493@emeril.freedesktop.org> (raw)
In-Reply-To: <20190919201204.9691-1-daniele.ceraolospurio@intel.com>
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/uc: Update HuC firmware naming convention and load latest HuC
URL : https://patchwork.freedesktop.org/series/66955/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c63f361673b5 drm/i915/uc: Update HuC firmware naming convention and load latest HuC
8e2004a0d670 HAX: force enable_guc=2
-:7: WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 0 checks, 8 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-19 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 20:12 [CI 1/2] drm/i915/uc: Update HuC firmware naming convention and load latest HuC Daniele Ceraolo Spurio
2019-09-19 20:12 ` [CI 2/2] HAX: force enable_guc=2 Daniele Ceraolo Spurio
2019-09-19 22:35 ` Patchwork [this message]
2019-09-19 23:02 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/uc: Update HuC firmware naming convention and load latest HuC Patchwork
2019-09-20 12:51 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-09-20 18:04 ` Daniele Ceraolo Spurio
-- strict thread matches above, loose matches on Subject: below --
2019-09-13 18:35 [CI 1/2] " Anusha Srivatsa
2019-09-13 18:52 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/2] " 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=20190919223530.23914.56493@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox