On Thu, Dec 13, 2012 at 08:27:41AM +1100, Stephen Rothwell wrote: > Hi, > > On Wed, 12 Dec 2012 10:03:38 +0000 Mel Gorman <mgor...@suse.de> wrote: > > > > This is a pull request for "Automatic NUMA Balancing V11". The list > > of changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681: > > > > Linux 3.7-rc6 (2012-11-16 17:42:40 -0800) > > > > are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux-balancenuma.git > > balancenuma-v11 > > > > for you to fetch changes up to 4fc3f1d66b1ef0d7b8dc11f4ff1cc510f78b37d6: > > > > mm/rmap, migration: Make rmap_walk_anon() and try_to_unmap_anon() more > > scalable (2012-12-11 14:43:00 +0000) > > > > <SNIP> > > These reports were quite late in the cycle so I/we would like to start > > with this tree as it contains much of the code we can agree on and has > > not changed significantly over the last 2-3 weeks. > > It has, however all been rebased from what still exists in the linux-next > tree (as part of the tip tree). >
What's in the tip tree is not the same even though there are similarities. I know that bypassing linux-next like this is not the done thing but it was not possible to have this tree in linux-next before now. After this mail https://lkml.org/lkml/2012/12/11/62 my expectation is that that the numacore bits from tip that were included in linux-next will not be pulled this time. However, due to some of the similarities I'm hoping that the collisions due to pulling this tree will not be too severe. -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
