From: Chris Wilson <chris@chris-wilson.co.uk>
To: Georg Grabler <georg@grabler.net>, intel-gfx@lists.freedesktop.org
Subject: Re: Testing intel-drm
Date: Fri, 01 Apr 2011 08:39:13 +0100 [thread overview]
Message-ID: <b9dded$ih82j5@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTinu8u2AN+_pkAnfhWstgPAgqagnR2C0adZQy7kk@mail.gmail.com>
On Fri, 1 Apr 2011 09:01:41 +0200, Georg Grabler <georg@grabler.net> wrote:
> Hi Guys,
>
> Just a question since I opened two bug reports lately (35808, 35812), I
> wanted to ask which intel-drm branches you generally would like the test
> against. I tested against 2.6.38.2 for now, but to have it tested against
> your current developments - which branch to use? intel-drm-next or
> intel-drm-fixes, or both?
For an outright bug like you have found, we should try to get a stable
patch. So drm-intel-fixes is where it should land first. On the other
hand, if fixing the issue is complicated then we would have no choice but
to let it sit on drm-intel-next so that we more opportunity to run more
regression tests upon it.
However, we first need to get a patch ready for you to test. :|
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-04-01 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 7:01 Testing intel-drm Georg Grabler
2011-04-01 7:39 ` Chris Wilson [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='b9dded$ih82j5@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=georg@grabler.net \
--cc=intel-gfx@lists.freedesktop.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