All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not
Date: Wed, 15 Nov 2017 19:11:45 +0200	[thread overview]
Message-ID: <20171115171145.GL10981@intel.com> (raw)
In-Reply-To: <20171102151737.23336-1-ville.syrjala@linux.intel.com>

I pushed the series to dinq. Thanks for the review.

I think we can re-evaluate the case for the lock bit if and when someone
reports seeing the DRM_ERROR() in the wild.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-11-15 17:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 15:17 [PATCH 1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Ville Syrjala
2017-11-02 15:17 ` [PATCH 2/3] drm/i915: Make the report about a bogus stolen reserved area an error Ville Syrjala
2017-11-14 20:33   ` Paulo Zanoni
2017-11-14 20:41     ` Ville Syrjälä
2017-11-02 15:17 ` [PATCH 3/3] drm/i915: Use ELK stolen memory reserved detection for ILK Ville Syrjala
2017-11-14 20:59   ` Paulo Zanoni
2017-11-14 21:19     ` Ville Syrjälä
2017-11-02 15:38 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Patchwork
2017-11-02 16:34 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-02 17:08   ` Ville Syrjälä
2017-11-03  7:19     ` Saarinen, Jani
2017-11-03  8:18     ` Tomi Sarvela
2017-11-03 10:41       ` Ville Syrjälä
2017-11-03 11:14         ` Tomi Sarvela
2017-11-03 10:43       ` Petri Latvala
2017-11-03 11:33         ` Tomi Sarvela
2017-11-03 12:53           ` Tomi Sarvela
2017-11-03 12:52 ` ✓ Fi.CI.IGT: success " Patchwork
2017-11-14 20:12 ` [PATCH 1/3] " Paulo Zanoni
2017-11-14 20:19   ` Chris Wilson
2017-11-14 20:29     ` Paulo Zanoni
2017-11-14 20:41       ` Chris Wilson
2017-11-14 20:34   ` Ville Syrjälä
2017-11-14 20:44     ` Paulo Zanoni
2017-11-14 21:38       ` Ville Syrjälä
2017-11-15 17:11 ` Ville Syrjälä [this message]

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=20171115171145.GL10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=tomi.p.sarvela@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.