From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 00/10] drm-intel-collector - update
Date: Thu, 6 Nov 2014 09:57:29 +0200 [thread overview]
Message-ID: <20141106075729.GN10649@intel.com> (raw)
In-Reply-To: <1415105508-1590-1-git-send-email-rodrigo.vivi@intel.com>
On Tue, Nov 04, 2014 at 04:51:38AM -0800, Rodrigo Vivi wrote:
>
> This is another drm-intel-collector updated notice:
> http://cgit.freedesktop.org/~vivijim/drm-intel/log/?h=drm-intel-collector
>
> Here goes the update list in order for better reviewers assignment:
>
> Patch drm/i915: Check the minimum pitch for the user framebuffer - Reviewer:
My comment still stands that the core checks should have caught this.
Actually now I think about it, addfb didn't call framebuffer_check()
until very recently, which could explain this. So the problem might be
fixed by
commit 228f2cb32f0dbeef0b88dc97ea66a3c31b03de99
Author: Chuck Ebbert <cebbert.lkml@gmail.com>
Date: Wed Oct 8 11:40:34 2014 -0500
drm/crtc: Remove duplicated ioctl code
> Patch drm/i915: Make the physical object coherent with GTT - Reviewer:
Already has my r-b.
> Patch drm/i915: Enable vblank interrupts for CRC generation - Reviewer:
IIRC everyone agreed that this isn't needed.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-06 7:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 12:51 [PATCH 00/10] drm-intel-collector - update Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 01/10] drm/i915: Check the minimum pitch for the user framebuffer Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 02/10] drm/i915: Make the physical object coherent with GTT Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 03/10] drm/i915/chv: Use timeout mode for RC6 on chv Rodrigo Vivi
2014-11-04 22:36 ` O'Rourke, Tom
2014-11-04 12:51 ` [PATCH 04/10] drm/i915: Specify bsd rings through exec flag Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 05/10] drm/i915: add I915_PARAM_HAS_BSD2 to i915_getparam Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 06/10] drm/i915: Enable vblank interrupts for CRC generation Rodrigo Vivi
2014-11-06 8:31 ` Damien Lespiau
2014-11-04 12:51 ` [PATCH 07/10] drm/i915: Move the ban period onto the context Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 08/10] drm/i915: Add ioctl to set per-context parameters Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 09/10] drm/i915: Put logical pipe_control emission into a helper Rodrigo Vivi
2014-11-04 12:51 ` [PATCH 10/10] drm/i915: Add WaCsStallBeforeStateCacheInvalidate:bdw, chv to logical ring Rodrigo Vivi
2014-11-06 0:42 ` [PATCH 00/10] drm-intel-collector - update Rodrigo Vivi
2014-11-06 7:57 ` Ville Syrjälä [this message]
2014-11-11 10:20 ` Daniel Vetter
2014-11-11 10:22 ` Chris Wilson
2014-11-11 11:54 ` Daniel Vetter
2014-11-11 11:57 ` Chris Wilson
2014-11-11 14:48 ` Daniel Vetter
2014-11-11 12:16 ` Ville Syrjälä
2014-11-11 12:26 ` Chris Wilson
2014-11-11 12:38 ` Ville Syrjälä
2014-11-11 12:43 ` Chris Wilson
2014-11-11 14:50 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-07-03 21:32 Rodrigo Vivi
2014-07-08 19:09 ` Daniel Vetter
2014-07-03 21:31 Rodrigo Vivi
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=20141106075729.GN10649@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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