From: Patchwork <patchwork@emeril.freedesktop.org>
To: Anusha <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for HuC Updates [BXT,SKL,KBL,GLK] GuC [GLK] (rev2)
Date: Wed, 28 Nov 2018 23:18:30 -0000 [thread overview]
Message-ID: <20181128231830.30718.3972@emeril.freedesktop.org> (raw)
In-Reply-To: <20181128213452.18821-1-anusha.srivatsa@intel.com>
== Series Details ==
Series: HuC Updates [BXT,SKL,KBL,GLK] GuC [GLK] (rev2)
URL : https://patchwork.freedesktop.org/series/53191/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2f174cb3de1c firmware/huc/BXT: Update the HuC version
495993ba9aed firmware/huc/SKL: Update HuC versiom for SKL
a6b97b520d1d firmware/huc/KBL: Update HuC for KBL
afc0b5259f0b firmware/huc/GLK: Load HuC for GLK
4fdcb5ba00ae firmware/guc/glk: Load GuC v11.98 for Geminilake.
1a987393fb1b HAX enable HuC for CI
-: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:[~2018-11-28 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:34 [PATCH 0/6] HuC Updates [BXT,SKL,KBL,GLK] GuC [GLK] Anusha
2018-11-28 21:34 ` [PATCH 1/6] firmware/huc/BXT: Update the HuC version Anusha
2018-11-28 21:34 ` [PATCH 2/6] firmware/huc/SKL: Update HuC versiom for SKL Anusha
2018-11-28 21:34 ` [PATCH 3/6] firmware/huc/KBL: Update HuC for KBL Anusha
2018-11-28 21:34 ` [PATCH 4/6] firmware/huc/GLK: Load HuC for GLK Anusha
2018-11-28 21:34 ` [PATCH 5/6] firmware/guc/glk: Load GuC v11.98 for Geminilake Anusha
2018-11-28 21:34 ` [PATCH 6/6] HAX enable HuC for CI Anusha
2018-11-28 23:18 ` Patchwork [this message]
2018-11-28 23:40 ` ✗ Fi.CI.BAT: failure for HuC Updates [BXT,SKL,KBL,GLK] GuC [GLK] (rev2) 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=20181128231830.30718.3972@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=anusha.srivatsa@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