From: "François Valenduc" <francoisvalenduc@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: commit 319c1d420a0b (Ensure plane->state->fb stays in sync with plane->fb) cause various errors
Date: Mon, 23 Mar 2015 19:49:03 +0100 [thread overview]
Message-ID: <5510601F.1070609@gmail.com> (raw)
In-Reply-To: <87pp80t7si.fsf@intel.com>
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-23 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 16:26 commit 7ce42ae67c49204c0b2252edd06f7920e0a51037 cause various errors François Valenduc
2015-03-23 8:52 ` Jani Nikula
2015-03-23 18:49 ` François Valenduc [this message]
2015-03-23 19:03 ` commit 319c1d420a0b (Ensure plane->state->fb stays in sync with plane->fb) " Jani Nikula
2015-03-24 7:35 ` Daniel Vetter
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=5510601F.1070609@gmail.com \
--to=francoisvalenduc@gmail.com \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.