From: Daniel Vetter <daniel@ffwll.ch>
To: "Sun, Yi" <yi.sun@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Updated -next
Date: Sat, 21 Jan 2012 15:12:08 +0100 [thread overview]
Message-ID: <20120121141208.GA3821@phenom.ffwll.local> (raw)
In-Reply-To: <D9F66AA509623343B6A9A3D4502D5A520FCAECA2@SHSMSX102.ccr.corp.intel.com>
On Sat, Jan 21, 2012 at 04:15:40AM +0000, Sun, Yi wrote:
> > Hi all,
> >
> > Not much in the first -next update under the new process, I'd like to
> > tests the qa process first. Highligths:
> > - first part of i9xx_crtc_mode_set refactor from Jesse
> > - quite a few ajax-is-paranoid patches
> > - HAS_LLC param from Eugeni
> > - kill i915_mem.c
> >
> > For easier testing there's also an updated drm-intel-testing branch with
> > the latest -fixes merged in (i.e. the missed irq patches). Testing
> > feedback highly welcome.
> >
> > Hi Yi,
> >
> > Please put the -testing branch through the kernel qa process. Btw I've
> > noticed that the nightly tests are missing a few recent i-g-t tests,
> > please upgrade that.
> >
>
> I'm confused about branch drm-intel-testing. Does it mean drm-intel-next
> branch when you said branch drm-intel-testing?
drm-intel-testing is drm-intel-next and drm-intel-fixes merged together
(as the time of when I've pushed things out). Gordon Jin said that he
prefers to qa one single branch and that qa will take the job of finding
out whether an issue has been introduced in -fixes or in -next. I agree
that it makes more sense to test everything together, otherwise you'll
miss some of the bugfixes in -fixes.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-01-21 14:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 10:10 Updated -next Daniel Vetter
2012-01-21 4:15 ` Sun, Yi
2012-01-21 14:12 ` Daniel Vetter [this message]
2012-01-21 19:45 ` Alan W. Irwin
2012-01-31 9:07 ` Jin, Gordon
2012-02-07 22:59 updated -next Daniel Vetter
2012-02-16 17:27 Daniel Vetter
2012-02-17 17:56 ` Jesse Barnes
2012-02-21 7:45 ` Sun, Yi
2012-03-01 20:59 Updated -next Daniel Vetter
2012-03-08 8:10 ` Sun, Yi
2012-03-18 21:20 ` Daniel Vetter
2012-03-23 10:03 Daniel Vetter
2012-03-29 7:38 ` Sun, Yi
2012-04-05 9:45 Daniel Vetter
2012-04-09 16:19 ` Daniel Vetter
2012-04-10 2:09 ` Sun, Yi
2012-04-11 3:20 ` Sun, Yi
2012-04-11 7:54 ` Paul Menzel
2012-04-11 8:24 ` Sun, Yi
2012-04-11 9:45 ` Paul Menzel
2012-04-21 16:40 Daniel Vetter
2012-04-23 7:39 ` Daniel Vetter
2012-04-23 7:40 ` Sun, Yi
2012-04-27 11:45 ` Daniel Vetter
2012-04-27 13:44 ` Daniel Vetter
2012-05-06 19:09 Daniel Vetter
2012-06-04 20:59 Daniel Vetter
2012-06-12 8:37 ` Daniel Vetter
2012-06-21 8:25 Daniel Vetter
2012-07-22 14:33 updated -next 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=20120121141208.GA3821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yi.sun@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.