On Sun, 23 Mar 2014, kbuild test robot wrote: > >> mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block > >> arch/x86/include/asm/paravirt.h:699:9: sparse: context imbalance in 'change_pte_range' - unexpected unlock > -- > >> fs/ntfs/super.c:3100:1: sparse: directive in argument list > >> fs/ntfs/super.c:3102:1: sparse: directive in argument list > >> fs/ntfs/super.c:3104:1: sparse: directive in argument list > >> fs/ntfs/super.c:3105:1: sparse: directive in argument list > >> fs/ntfs/super.c:3107:1: sparse: directive in argument list > >> fs/ntfs/super.c:3108:1: sparse: directive in argument list > >> fs/ntfs/super.c:3110:1: sparse: directive in argument list Looked through these and I am a bit puzzled how they related to raw cpu ops patch. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>