Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757386Ab1CXXtT (ORCPT ); Thu, 24 Mar 2011 19:49:19 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:49912 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757309Ab1CXXtQ (ORCPT ); Thu, 24 Mar 2011 19:49:16 -0400 MIME-Version: 1.0 In-Reply-To: References: <1300864998.3522.71.camel@thor.local> <1300868532.3522.81.camel@thor.local> <1300880747.16522.13.camel@thor.local> From: Linus Torvalds Date: Thu, 24 Mar 2011 16:48:21 -0700 Message-ID: Subject: Re: [git pull] drm fixes To: Dave Airlie Cc: Ilija Hadzic , =?ISO-8859-1?Q?Michel_D=E4nzer?= , linux-kernel@vger.kernel.org, DRI mailing list Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 23 On Thu, Mar 24, 2011 at 1:05 PM, Dave Airlie wrote: > > If you think this has anything to do with Intel's ability to break your hardware > on every merge then you've got your wires crossed. No, it's about the fact that I expect to be pushed code that is WRITTEN AND TESTED BEFORE THE MERGE WINDOW. The merge window is not for writing new code. The code that gets merged should have been written two weeks ago already. The only new code that I want to see are actual regressions. I have been talking about this for YEARS now. It's not a new issue. I hate seeing patches sent to me while they are clearly still being discussed and developed. There's something seriously wrong there when that happens. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/