From: Chris Wilson <chris@chris-wilson.co.uk>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: airlied@redhat.com, stable@vger.kernel.org,
dri-devel@lists.freedesktop.org, Lu Huax <huax.lu@intel.com>
Subject: Re: [PATCH] drm: Destroy the planes prior to destroying the associated CRTC
Date: Wed, 19 Sep 2012 11:26:10 +0100 [thread overview]
Message-ID: <453bf0$5pemmt@azsmga001.ch.intel.com> (raw)
In-Reply-To: <1348047934.4196.25.camel@mattotaupa>
On Wed, 19 Sep 2012 11:45:34 +0200, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> Am Mittwoch, den 19.09.2012, 11:34 +0200 schrieb Daniel Vetter:
> > On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> > > On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > > > Yeah, looks good. Did we used to not touch the crtc in the plane
> > > > cleanup? Either way this is safer.
> > >
> > > I think the bug only came to light because QA is now routinely running
> > > with slub_debug.
> >
> > And QA now confirmed that this patch fixes things:
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
> > Tested-by: lu hua <huax.lu@intel.com>
>
> Lu Hua*x*?
The 'x' is just part of Intel's policy for indicating a contractor in
email addresses, which can be quite confusing.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-19 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 9:38 [PATCH] drm: Destroy the planes prior to destroying the associated CRTC Chris Wilson
2012-09-17 14:55 ` Jesse Barnes
2012-09-17 15:04 ` Chris Wilson
2012-09-19 9:34 ` Daniel Vetter
2012-09-19 9:45 ` Paul Menzel
2012-09-19 10:26 ` Chris Wilson [this message]
2012-09-20 2:52 ` Joonyoung Shim
2012-09-20 5:38 ` Rob Clark
2012-09-20 6:10 ` Joonyoung Shim
2012-09-20 7:49 ` Chris Wilson
2012-09-20 8:08 ` Joonyoung Shim
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='453bf0$5pemmt@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=huax.lu@intel.com \
--cc=paulepanter@users.sourceforge.net \
--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