On Wed, Feb 22, 2006 at 12:35:49PM +0000, Mel Gorman wrote: > >One request regarding file names - our tools key off of the patch name > >to determine which kernel to apply against. Would it be possible for > >you to create symlinks to the patch that include the kernel or kernels > >you'd like to test against? I.e., to test zbuddy-v5 against multiple > >2.6.16-rc3 kernels, something like: > > > >.../zbuddy/v5/ > > 2.6.16-rc3-zbuddy-v5 -> zbuddy-v5-full.diff > > 2.6.16-rc3-mm1-zbuddy-v5 -> zbuddy-v5-full.diff > > 2.6.16-rc3-mm2-zbuddy-v5 -> zbuddy-v5-full.diff > > 2.6.16-rc3-mm3-zbuddy-v5 -> zbuddy-v5-full.diff Hi Mel, In the above I made a small mistake. Judith says the tool keys off of the file extension, so the links should have the .diff extension. I.e.: 2.6.16-rc3-zbuddy-v5.diff -> zbuddy-v5-full.diff 2.6.16-rc3-mm1-zbuddy-v5.diff -> zbuddy-v5-full.diff We've manually pulled one the -v22 patch, run against 2.6.16-rc1-mm1 kernel. The raw results are here: http://www.testing.osdl.org/plm-cgi/plm?module=patch_info&patch_id=5017 Looking through the data, I spotted one thing that looked interesting. When configuring with allnoconfig, I noticed this warning appears for i386 and ppc: CC arch/i386/kernel/vm86.o mm/vmscan.c: In function `remove_mapping': mm/vmscan.c:397: warning: unused variable `swap' http://www.testing.osdl.org/projects/plm/results/5017/i386.cr/2.6.16-rc1-mm1.allnoconfig.bzImage.txt.gz The other failures it picked up are also appearing in the base kernel so are not relevant for memory hotplug. There do not appear to be any other hotplug-memory compile issues in this patch. Bryce
