From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <benjamin.widawsky@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/hsw: Implement Selective Write workaround
Date: Mon, 5 Jan 2015 11:02:37 +0100 [thread overview]
Message-ID: <20150105100237.GS2711@phenom.ffwll.local> (raw)
In-Reply-To: <20141219221430.GA1700@bwidawsk.net>
On Fri, Dec 19, 2014 at 02:14:31PM -0800, Ben Widawsky wrote:
> On Fri, Dec 19, 2014 at 08:05:30PM +0000, Chris Wilson wrote:
> > On Fri, Dec 19, 2014 at 06:34:07PM +0000, Chris Wilson wrote:
> > > Just a patch a few days ago that to fix a very ontologically similar bug
> > > for ivb+.
> >
> > Oh boy. I just double checked the error states from those bugs I marked
> > as ivb context restore hangs... So far I appear to have consistently
> > mislabled 0x402/0x406 as ivb and not hsw gt1. /o\
> > -Chris
>
> I don't know what to do with this patch now. It looks like all we needed was
> your patch. Merge without the "stable" is what I'm thinking.
Makes sense if we really don't need it any more with Chris' patches in
-fixes. Can you please volunteer someone to cough up an r-b?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-01-05 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 2:20 [PATCH] drm/i915/hsw: Implement Selective Write workaround Ben Widawsky
2014-12-19 8:20 ` [Intel-gfx] " Chris Wilson
2014-12-19 17:26 ` Ben Widawsky
2014-12-19 18:34 ` [Intel-gfx] " Chris Wilson
2014-12-19 20:05 ` Chris Wilson
2014-12-19 22:14 ` Ben Widawsky
2015-01-05 10:02 ` Daniel Vetter [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=20150105100237.GS2711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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