All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matt Roper" <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/tgl: Program BW_BUDDY registers during display init (rev2)
Date: Thu, 05 Dec 2019 05:35:31 -0000	[thread overview]
Message-ID: <157552413125.19945.4384055521286025972@emeril.freedesktop.org> (raw)
In-Reply-To: <20191204205159.4062990-1-matthew.d.roper@intel.com>

== Series Details ==

Series: drm/i915/tgl: Program BW_BUDDY registers during display init (rev2)
URL   : https://patchwork.freedesktop.org/series/70461/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915/tgl: Program BW_BUDDY registers during display init
+drivers/gpu/drm/i915/display/intel_display_power.c:4790:30: warning: symbol 'tgl_buddy_page_masks' was not declared. Should it be static?

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

  parent reply	other threads:[~2019-12-05  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 20:51 [Intel-gfx] [PATCH] drm/i915/tgl: Program BW_BUDDY registers during display init Matt Roper
2019-12-05  1:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-12-05  1:46 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2019-12-05  1:51   ` Matt Roper
2019-12-05  5:35 ` Patchwork [this message]
2019-12-05  5:56 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/tgl: Program BW_BUDDY registers during display init (rev2) Patchwork
2019-12-05  8:34 ` [Intel-gfx] [PATCH] drm/i915/tgl: Program BW_BUDDY registers during display init Lisovskiy, Stanislav
2019-12-05 17:19 ` Lucas De Marchi
2019-12-05 17:31   ` Ville Syrjälä
2019-12-05 19:26     ` Lucas De Marchi

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=157552413125.19945.4384055521286025972@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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.