Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757019AbZDRI7X (ORCPT ); Sat, 18 Apr 2009 04:59:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751020AbZDRI7O (ORCPT ); Sat, 18 Apr 2009 04:59:14 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:60872 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750760AbZDRI7O (ORCPT ); Sat, 18 Apr 2009 04:59:14 -0400 Date: Sat, 18 Apr 2009 01:59:05 -0700 (PDT) Message-Id: <20090418.015905.92829818.davem@davemloft.net> To: eric@anholt.net Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [git pull] Fixes to 2.6.30rc2 From: David Miller In-Reply-To: <1240001399.11172.121.camel@gaiman.anholt.net> References: <1240001399.11172.121.camel@gaiman.anholt.net> X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 922 Lines: 22 From: Eric Anholt Date: Fri, 17 Apr 2009 13:49:59 -0700 > git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel drm-intel-next Eric, any plans to ever push your work through David Airlie's DRM tree? I've been watching this for a few weeks and I'm mystified why the Intel DRM drier stuff is so special that is always goes seperate. It's seems foolish for David to manage the infrastructure and core DRM changes, as well as those for radeon and the other drivers other than Intel, which could potentially cause merge issues and conflicts with your driver changes. Why not do Intel DRM driver development via his tree? I just don't get it. :-/ -- 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/