Subject: [patch 0/6] x86: apicdef.h unification

The following patch series unifies apicdef*h header files for the x86
architure. For a better review there are many small patches.


--
Advanced Micro Devices, Inc.
Operating System Research Center
email: [email protected]




2007-11-06 20:32:39

by Thomas Gleixner

[permalink] [raw]
Subject: Re: [patch 0/6] x86: apicdef.h unification

Robert,

On Tue, 6 Nov 2007, Robert Richter wrote:

> The following patch series unifies apicdef*h header files for the x86
> architure. For a better review there are many small patches.


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.

Thanks,

tglx

Subject: Re: [patch 0/6] x86: apicdef.h unification

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.

-Robert

--
Advanced Micro Devices, Inc.
Operating System Research Center
email: [email protected]


2007-11-08 17:54:12

by Thomas Gleixner

[permalink] [raw]
Subject: Re: [patch 0/6] x86: apicdef.h unification



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