linux-kernel - Re: Including drm-intel tree to linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130216012608.095525f7910901e2b479c2cf@canb.auug.org.au>
Date:	Sat, 16 Feb 2013 01:26:08 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Daniel Vetter <daniel.vetter@...ll.ch>
Cc:	Borislav Petkov <bp@...en8.de>, rostedt@...dmis.org,
	Dave Airlie <airlied@...il.com>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Including drm-intel tree to linux-next

Hi Daniel,

On Fri, 15 Feb 2013 10:43:52 +0100 Daniel Vetter <daniel.vetter@...ll.ch> wrote:
>
> The patches in my next queue are fully reviewed and (should) have seen
> at least basic testing. The additional QA on top is just normal
> regression testing and about every 2 weeks a manual testing cycle for
> things like hotplug on the bazillion configurations we support (since
> that takes our QA team about 1 week to complete we can't do higher
> frequency there). The reason we've put that next queue buffer into
> place was that before the pulls to Dave received essentially 0 testing
> from our QA, resulting in lots more regressions slipping through.
> -next-queued is also what I run here on all my machines and what patch
> development is usually based on for drm/i915.
> 
> Does that put your concerns at ease?

Some what, thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped