Prev: [PATCH] AFS: Fix possible null pointer dereference in afs_alloc_server()
Next: [GIT PULL] rcu: finalize debugobjects, first round of RCU sparse pointer checks
From: Randy Dunlap on 1 Jun 2010 13:00 From: Randy Dunlap <randy.dunlap(a)oracle.com> We should only build hpet_example on (any) X86, where it is implemented. It can cause build errors on other arch-es. Signed-off-by: Randy Dunlap <randy.dunlap(a)oracle.com> Reported-by: Heiko Carstens <heiko.carstens(a)de.ibm.com> Cc: Heiko Carstens <heiko.carstens(a)de.ibm.com> Cc: Arjan van de Ven <arjan(a)infradead.org> --- Documentation/timers/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- lnx-2635-rc1.orig/Documentation/timers/Makefile +++ lnx-2635-rc1/Documentation/timers/Makefile @@ -2,7 +2,7 @@ obj- := dummy.o # List of programs to build -hostprogs-y := hpet_example +hostprogs-$(CONFIG_X86) := hpet_example # Tell kbuild to always build the programs always := $(hostprogs-y) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |