Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [01/15] drm/i915/guc: Tidy guc_log_control
Date: Tue, 27 Feb 2018 13:38:05 -0000	[thread overview]
Message-ID: <20180227133805.30095.98298@emeril.freedesktop.org> (raw)
In-Reply-To: <20180227125230.13000-1-michal.winiarski@intel.com>

== Series Details ==

Series: series starting with [01/15] drm/i915/guc: Tidy guc_log_control
URL   : https://patchwork.freedesktop.org/series/39043/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Commit: drm/i915/guc: Tidy guc_log_control
Okay!

Commit: drm/i915/guc: Create common entry points for log register/unregister
+drivers/gpu/drm/i915/intel_guc_log.c:444:5: warning: symbol 'guc_log_relay_create' was not declared. Should it be static?
+drivers/gpu/drm/i915/intel_guc_log.c:497:6: warning: symbol 'guc_log_relay_destroy' was not declared. Should it be static?

Commit: drm/i915/guc: Move GuC notification handling to separate function
Okay!

Commit: drm/i915/guc: Keep GuC interrupts enabled when using GuC
Okay!

Commit: drm/i915/guc: Log runtime should consist of both mapping and relay
-O:drivers/gpu/drm/i915/intel_guc_log.c:497:6: warning: symbol 'guc_log_relay_destroy' was not declared. Should it be static?
+drivers/gpu/drm/i915/intel_guc_log.c:459:6: warning: symbol 'guc_log_relay_destroy' was not declared. Should it be static?

Commit: drm/i915/guc: Merge log relay file and channel creation
Okay!

Commit: drm/i915/guc: Flush directly in log unregister
Okay!

Commit: drm/i915/guc: Split relay control and GuC log level
Okay!

Commit: drm/i915/guc: Move check for fast memcpy_wc to relay creation
Okay!

Commit: drm/i915/guc: Get rid of GuC log runtime
-O:drivers/gpu/drm/i915/intel_guc_log.c:376:5: warning: symbol 'guc_log_relay_create' was not declared. Should it be static?
-O:drivers/gpu/drm/i915/intel_guc_log.c:423:6: warning: symbol 'guc_log_relay_destroy' was not declared. Should it be static?
+drivers/gpu/drm/i915/intel_guc_log.c:376:5: warning: symbol 'guc_log_relay_create' was not declared. Should it be static?
+drivers/gpu/drm/i915/intel_guc_log.c:423:6: warning: symbol 'guc_log_relay_destroy' was not declared. Should it be static?

Commit: drm/i915/guc: Always print log stats in i915_guc_info when using GuC
Okay!

Commit: drm/i915/guc: Don't print out relay statistics when relay is disabled
Okay!

Commit: drm/i915/guc: Allow user to control default GuC logging
Okay!

Commit: drm/i915/guc: Default to non-verbose GuC logging
Okay!

Commit: HAX enable guc and guc_log for CI
Okay!

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

  parent reply	other threads:[~2018-02-27 13:38 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 12:52 [PATCH 01/15] drm/i915/guc: Tidy guc_log_control Michał Winiarski
2018-02-27 12:52 ` [PATCH 02/15] drm/i915/guc: Create common entry points for log register/unregister Michał Winiarski
2018-02-27 14:11   ` Michal Wajdeczko
2018-03-05  7:09   ` Sagar Arun Kamble
2018-03-05 13:38     ` Michał Winiarski
2018-03-06  5:24       ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 03/15] drm/i915/guc: Move GuC notification handling to separate function Michał Winiarski
2018-03-05  7:40   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 04/15] drm/i915/guc: Keep GuC interrupts enabled when using GuC Michał Winiarski
2018-03-05  9:27   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 05/15] drm/i915/guc: Log runtime should consist of both mapping and relay Michał Winiarski
2018-02-27 14:21   ` Michal Wajdeczko
2018-03-05 10:31   ` Sagar Arun Kamble
2018-03-05 14:14     ` Michał Winiarski
2018-03-06  5:54       ` Sagar Arun Kamble
2018-03-06 13:50   ` Chris Wilson
2018-02-27 12:52 ` [PATCH 06/15] drm/i915/guc: Merge log relay file and channel creation Michał Winiarski
2018-03-05 11:44   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 07/15] drm/i915/guc: Flush directly in log unregister Michał Winiarski
2018-03-05 11:58   ` Sagar Arun Kamble
2018-03-05 12:10     ` Michał Winiarski
2018-03-06  4:59       ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 08/15] drm/i915/guc: Split relay control and GuC log level Michał Winiarski
2018-03-06  7:16   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 09/15] drm/i915/guc: Move check for fast memcpy_wc to relay creation Michał Winiarski
2018-02-27 14:37   ` Michal Wajdeczko
2018-02-27 15:37     ` Michał Winiarski
2018-03-06 14:00       ` Chris Wilson
2018-03-06  7:23   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 10/15] drm/i915/guc: Get rid of GuC log runtime Michał Winiarski
2018-03-06  9:30   ` Sagar Arun Kamble
2018-03-06 14:02   ` Chris Wilson
2018-02-27 12:52 ` [PATCH 11/15] drm/i915/guc: Always print log stats in i915_guc_info when using GuC Michał Winiarski
2018-03-06  7:41   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 12/15] drm/i915/guc: Don't print out relay statistics when relay is disabled Michał Winiarski
2018-03-06 11:21   ` Sagar Arun Kamble
2018-03-06 12:00     ` Michał Winiarski
2018-03-06 13:16   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 13/15] drm/i915/guc: Allow user to control default GuC logging Michał Winiarski
2018-03-06 11:58   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 14/15] drm/i915/guc: Default to non-verbose " Michał Winiarski
2018-03-06 13:44   ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 15/15] HAX enable guc and guc_log for CI Michał Winiarski
2018-02-27 13:38 ` Patchwork [this message]
2018-02-27 13:47 ` ✓ Fi.CI.BAT: success for series starting with [01/15] drm/i915/guc: Tidy guc_log_control Patchwork
2018-02-27 13:49 ` [PATCH 01/15] " Michal Wajdeczko
2018-02-27 20:10 ` ✗ Fi.CI.IGT: failure for series starting with [01/15] " Patchwork
2018-03-02 11:09 ` [PATCH 01/15] " Sagar Arun Kamble
2018-03-02 11:52   ` Michał Winiarski
2018-03-05  5:29     ` Sagar Arun Kamble

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=20180227133805.30095.98298@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.winiarski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox