Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761702AbXKHRyM (ORCPT ); Thu, 8 Nov 2007 12:54:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759781AbXKHRx6 (ORCPT ); Thu, 8 Nov 2007 12:53:58 -0500 Received: from www.tglx.de ([62.245.132.106]:56656 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758744AbXKHRx6 (ORCPT ); Thu, 8 Nov 2007 12:53:58 -0500 Date: Thu, 8 Nov 2007 18:53:46 +0100 (CET) From: Thomas Gleixner To: Robert Richter cc: Ingo Molnar , "H. Peter Anvin" , LKML Subject: Re: [patch 0/6] x86: apicdef.h unification In-Reply-To: <20071108102411.GG20836@erda.amd.com> Message-ID: References: <20071106183645.951275000@amd.com> <20071108102411.GG20836@erda.amd.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 896 Lines: 26 On Thu, 8 Nov 2007, Robert Richter wrote: > Thomas, > > On 06.11.07 21:32:12, Thomas Gleixner wrote: > > Thanks for doing this, but please check the x86 git repository > > (cleanup / mm branch) for stuff which has been worked on already. > > > > Maybe we need some coordination for this. > > Is it for sure that the x86/cleanup tree will go upstream soon and the > source will not change as much? The question is what code base to use > for new patches? I want to keep the porting effort as small as > possible. We'll add patches on top of the cleanup branch. There should be not much changes, except if we have real functional changes. tglx - 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/