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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 Feb 2013 16:33:42 +0100
From:	Daniel Vetter <daniel.vetter@...ll.ch>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Borislav Petkov <bp@...en8.de>, 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>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: Including drm-intel tree to linux-next

On Thu, Feb 14, 2013 at 3:28 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 2013-02-14 at 15:19 +0100, Borislav Petkov wrote:
>> On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote:
>> > Hi Steven,
>> >
>> > Since about a year ago we've switched drm/i915 to buffer around 2
>> > weeks worth of patches so that we can do decent QA before breaking
>> > everyone's tree when things land in Dave's drm-next. But that also
>> > means we'll miss out a bit in the integration testing -next provides,
>> > which did hurt a bit in recent efforts. Hence can you please include
>> >
>> > git://people.freedesktop.org/~danvet/drm-intel drm-intel-next-queued
>> >
>> > into linux-next? Probably best to merge it after drm-next. Note that
>> > drm-intel-next are the QA'ed chunks I send off to Dave. Also, any
>> > mailing lists I'm supposed to follow? And if possible please cc
>> > intel-gfx@...ts.freedesktop.org besides dri-devel/lkml when conflicts
>> > with that tree pop up (you won't get moderation spam any more, we've
>> > fixed that up).
>>
>> I think you want to send this here to Stephen Rothwell. CCed.
>>
>
> This is why I tell people to call me Steve or Steven, but never Stephen,
> otherwise people might confuse me with one of the Stephens that also do
> kernel development.
>
> Note, this is not the first time I've been confused with someone else.
> So don't feel bad ;-)

Oops, indeed picked the wrong mail from my sea of "drm/i915 broke
stuff, again" mails ;-) Sorry for the noise, Steve.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/