[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080409151838.GC7648@cvg>
Date: Wed, 9 Apr 2008 19:18:38 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Jacek Luczak <difrost.kernel@...il.com>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for April 9
[Ingo Molnar - Wed, Apr 09, 2008 at 05:03:33PM +0200]
|
| * Cyrill Gorcunov <gorcunov@...il.com> wrote:
|
| > | > It seems that commit 883a9fc4e5d9b0701f15d4e5a23608f942104721
| > | > ("x86: cleanup - rename VM_MASK to X86_VM_MASK") from the x86 tree
| > | > seems to have missed some places.
| > |
| > | i think what happened is that some changes came in from other trees
| > | that reintroduced the old symbols?
| >
| > actually, that is the only explanation I could find. The last time I
| > sent you patches to fixup *all* VM_MASK (wich were grep'ed on *latest
| > branch over *all* sources inside x86). So this all were settled down
| > by a few of my patches and /for shame on me/ yours fixups. So these
| > fixups were missed on merging.
|
| no, the problem turned out to be that i kept those fixes too spread out,
| and part of them went into the x86/for-akpm portion of the tree, part of
| it went into x86/testing. Since all x86 developers work against
| x86/testing this was never a problem - only now did it become one when i
| shuffled patches and branch boundaries around. Such problems will go
| away once linux-next starts using x86/testing as well. In any case i
| moved your fixes together and fixed up the patch ordering as well.
|
| Ingo
|
ok, i see, thanks
- Cyrill -
--
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/
Powered by blists - more mailing lists