* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
Erm, no. In the merge window i follow upstream -git, not "my tree", and
i searched lkml for the build failure signature and it had nothing
there. Then i looked at the commit and it said that it was created just
1 day before the merge window started:
commit feac6a07c4a3578bffd6769bb4927e8a7e1f3ffe
Author: Martin Petermann <martin@linux.vnet.ibm.com>
AuthorDate: Wed Jul 2 10:56:35 2008 +0200
Commit: James Bottomley <James.Bottomley@HansenPartnership.com>
CommitDate: Sat Jul 12 08:22:34 2008 -0500
^^^^^^
So i didnt even think of it having hit linux-next so i didnt look into
the linux-next archives. lkml should have been Cc:-ed in this case,
that's where people look for in case of upstream breakages. You would
have saved me some effort via that - please try to do it in the future,
it's very helpful to testers.
btw., about the technical aspects of the solution, i'm not sure i like
these big #ifdef blocks:
the clean solution we use everywhere else is to push such #ifdefs into
the headers, to make them generally includable. For example you can
include lockdep.h even if you dont have lockdep enabled, you can include
smp.h even on UP-only files, etc. etc.
Ingo
--