From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Keith Packard <keithp@keithp.com>,
"Airlie, Dave" <airlied@linux.ie>,
Intel drivers <Intel-gfx@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PULL] drm-intel-next
Date: Thu, 5 Jan 2012 10:02:51 -0800 [thread overview]
Message-ID: <20120105100251.3fc7dfef@jbarnes-desktop> (raw)
In-Reply-To: <20120105152408.GD3831@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
On Thu, 5 Jan 2012 16:24:08 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:
> I'd also like to express my frustration with the general -next process for
> drm/i915:
> - This drm-intel-next tree is less than 24h ours old (if you look at when
> it showed up at an official place where both our QA and the community
> can pick it up and test it). I fear we'll ship yet another disaster like
> the stack eating bug the vt-d/ilk w/a patch caused with an unbounded
> recursion. Our QA actually caught it in testing, but there was simply
> not enough time to fix things up before the buggy code landed in -linus.
> - Because the drm-intel-next merge cycle started so late there has simply
> not been enough time to include quite a few bugfixes for serious issues
> like 20s delays in intial modeset, userspace-triggerable kernel OOPSes
> and deadlocks and reproducible hard hw hangs. For most of these there
> are testcases in intel-gpu-tools, and these issues span the entire set
> of hw generations drm/i915 currently supports. But this late it's imo
> no longer advisible to merge them, so we'll ship 3.3 with a bunch of
> known (and sometimes longstanding) serious issues that have fixes.
Yeah I have to second this and additionally complain about the patch
lossiness & latency. Part of this is my fault for not reviewing things
as much as I should, but those reviews often get lost too...
Eugeni's i2c patches are a good example. They've been out there since
early Oct, have received review and testing, and should have been in
-next for many months now (in previous releases!).
What can we do to improve the process to get trees updated more
regularly and get fixes integrated faster?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-05 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 3:35 [PULL] drm-intel-next Keith Packard
2012-01-05 15:24 ` Daniel Vetter
2012-01-05 17:58 ` [Intel-gfx] " Ben Widawsky
2012-01-05 18:02 ` Jesse Barnes [this message]
2012-09-13 14:18 [pull] drm-intel-next Daniel Vetter
2012-09-14 13:55 ` [Intel-gfx] " Bobby Powers
2012-09-14 15:43 ` Daniel Vetter
2012-09-14 19:52 ` Paulo Zanoni
2014-04-28 13:26 [PULL] drm-intel-next Daniel Vetter
2014-05-06 13:08 ` [Intel-gfx] " Knut Petersen
2014-05-06 13:30 ` Jani Nikula
2014-05-06 18:59 ` Daniel Vetter
2014-05-06 20:04 ` Knut Petersen
2014-05-06 20:17 ` [Intel-gfx] " Daniel Vetter
2015-12-22 10:37 Daniel Vetter
2015-12-22 14:05 ` Daniel Vetter
2015-12-22 14:31 ` Chris Wilson
2015-12-22 16:31 ` [Intel-gfx] " Tvrtko Ursulin
2015-12-23 10:09 ` Chris Wilson
2022-10-28 18:22 Rodrigo Vivi
2022-10-28 23:41 ` [Intel-gfx] " Ville Syrjälä
2022-11-01 22:29 ` Vivi, Rodrigo
2022-11-02 5:29 ` Ville Syrjälä
2023-03-07 22:00 Rodrigo Vivi
2023-03-08 13:24 ` [Intel-gfx] " Rodrigo Vivi
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=20120105100251.3fc7dfef@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).