public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Xi Ruoyao" <xry111@outlook.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"DRI mailing list" <dri-devel@lists.freedesktop.org>,
	"François Valenduc" <francoisvalenduc@gmail.com>
Subject: Re: commit 319c1d420a0b (Ensure plane->state->fb stays in sync with plane->fb) cause various errors
Date: Tue, 24 Mar 2015 08:35:45 +0100	[thread overview]
Message-ID: <20150324073545.GW1349@phenom.ffwll.local> (raw)
In-Reply-To: <871tkfo7ta.fsf@intel.com>

On Mon, Mar 23, 2015 at 09:03:13PM +0200, Jani Nikula wrote:
> 
> [adding more people and intel-gfx, original message with backtrace at
> http://mid.gmane.org/550EED22.9070008@gmail.com]
> 
> On Mon, 23 Mar 2015, François Valenduc <francoisvalenduc@gmail.com> wrote:
> > Le 23/03/15 09:52, Jani Nikula a écrit :
> >> On Sun, 22 Mar 2015, François Valenduc <francoisvalenduc@gmail.com> wrote:
> >>> It seems commit 7ce42ae67c49204c0b2252edd06f7920e0a51037 causes
> >>> several errors.
> >> It seems I don't have this commit. Which tree is this?
> >>
> >> I also admit to being pretty bad at associating commit ids with the
> >> actual commits, especially so for commit ids I don't have. It would be
> >> helpful to include the title of the commit too. ;)
> >>
> >> BR,
> >> Jani.
> >>
> >>
> > Sorry, the id I gave was the one of the revert I made in my local tree.
> > The problematic commit is the following:
> >
> > commit 319c1d420a0b62d9dbb88104afebaabc968cdbfa
> > Author: Xi Ruoyao <xry111@outlook.com>
> > Date:   Thu Mar 12 20:16:32 2015 +0800
> >
> >     drm/i915: Ensure plane->state->fb stays in sync with plane->fb
> >
> > This is a commit which has been merged in the mainline kernel tree
> > between 4.0-rc4 and 4.0-rc5.
> >
> >
> > Sincerely yours,
> >
> > François Valenduc

Please give drm-fixes a spin, specifically:

commit 8218c3f4df3bb1c637c17552405039a6dd3c1ee1
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Feb 27 12:58:13 2015 +0100

    drm: Fixup racy refcounting in plane_force_disable

http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-fixes&id=8218c3f4df3bb1c637c17552405039a6dd3c1ee1

Accidentally this landed in drm-next instead of -fixes at first.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-03-24  7:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550EED22.9070008@gmail.com>
     [not found] ` <87pp80t7si.fsf@intel.com>
     [not found]   ` <5510601F.1070609@gmail.com>
2015-03-23 19:03     ` commit 319c1d420a0b (Ensure plane->state->fb stays in sync with plane->fb) cause various errors Jani Nikula
2015-03-24  7:35       ` 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=20150324073545.GW1349@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francoisvalenduc@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=xry111@outlook.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