On Mon, Apr 29, 2013 at 09:06:37PM +0200, Jan Kiszka wrote: > > Bisect says that commit 4fb60de74f93a601775dbda053b3237634d7a417 > > That commit alone is broken as it depends on the refactorings being > selected by the submodule update. > > Does the problem persist with current master checked out into a clean > folder? OK, after further digging, following your canonical steps (i.e. "git submodule update --init") seems to work without problems. Instead, i was replacing the "linux" directory from kvm-kmod with a symlink to ../kvm (itself obtained via "git clone"), in a (potentially misguided) attempt to stay on the master branch of both projects. That *used* to work until the recent update. Now that I know I'm "off the reservation", I haven't yet figured out how "reasonable" vs. "bone-headed" of a thing that is... :) Any further clue much appreciated ! Thx, --Gabriel -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
