From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make unsupported fb modifier message DRM_DEBUG
Date: Wed, 25 Mar 2015 08:47:59 -0700 [thread overview]
Message-ID: <5512D8AF.2070808@virtuousgeek.org> (raw)
In-Reply-To: <20150325132847.GA1349@phenom.ffwll.local>
On 03/25/2015 06:28 AM, Daniel Vetter wrote:
> On Tue, Mar 24, 2015 at 10:19:59AM +0200, Jani Nikula wrote:
>> On Mon, 23 Mar 2015, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>>> Or users can just spam the log all they want.
>>>
>>> References: https://bugs.freedesktop.org/show_bug.cgi?id=89628
>>> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>>
>> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Queued for -next, thanks for the patch. And please reference the commit
> that introduce some broken code and cc author/reviewer of said commit.
> We're just going through some fun because a cherry-pick broke -rc and it's
> hard to find all the fixups in -next because they're not properly
> referenced.
In case you still want to update the log:
commit 9a8f0a1290993c86c4e35756a2624bfe461f9036
Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Date: Fri Feb 27 11:15:24 2015 +0000
drm/i915/skl: Allow Y (and Yf) frame buffer creation
Tvrtko already saw it though, this one just happened to slip through
when he converted the errors to debug once he was done debugging.
Jesse
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-25 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 19:43 [PATCH] drm/i915: make unsupported fb modifier message DRM_DEBUG Jesse Barnes
2015-03-24 8:19 ` Jani Nikula
2015-03-25 13:28 ` Daniel Vetter
2015-03-25 15:47 ` Jesse Barnes [this message]
2015-03-25 17:24 ` Daniel Vetter
2015-03-24 11:23 ` Tvrtko Ursulin
2015-03-24 14:33 ` Jesse Barnes
2015-03-25 3:44 ` shuang.he
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=5512D8AF.2070808@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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