The patch titled Subject: avr32: fix build error in ATSTK1002 code has been removed from the -mm tree. Its filename was avr32-fix-build-error-in-atstk1002-code.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Fengguang Wu <fengguang.wu@xxxxxxxxx> Subject: avr32: fix build error in ATSTK1002 code arch/avr32/boards/atstk1000/atstk1002.c:100: error: 'num_partitions' undeclared here (not in a function) which is introduced by commit 1754aab9bb86 ("mtd: ATMEL, AVR32: inline nand partition table access "). Signed-off-by: Fengguang Wu <fengguang.wu@xxxxxxxxx> Cc: Dmitry Eremin-Solenikov <dbaryshkov@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/avr32/boards/atstk1000/atstk1002.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN arch/avr32/boards/atstk1000/atstk1002.c~avr32-fix-build-error-in-atstk1002-code arch/avr32/boards/atstk1000/atstk1002.c --- a/arch/avr32/boards/atstk1000/atstk1002.c~avr32-fix-build-error-in-atstk1002-code +++ a/arch/avr32/boards/atstk1000/atstk1002.c @@ -97,7 +97,7 @@ static struct atmel_nand_data atstk1006_ .enable_pin = GPIO_PIN_PB(29), .ecc_mode = NAND_ECC_SOFT, .parts = nand_partitions, - .num_parts = ARRAY_SIZE(num_partitions), + .num_parts = ARRAY_SIZE(nand_partitions), }; #endif _ Patches currently in -mm which might be from fengguang.wu@xxxxxxxxx are origin.patch xtensa-select-generic-atomic64_t-support.patch mm-prepare-for-removal-of-obsolete-proc-sys-vm-nr_pdflush_threads.patch mm-clear-pages_scanned-only-if-draining-a-pcp-adds-pages-to-the-buddy-allocator-again.patch mm-slb-add-knowledge-of-pfmemalloc-reserve-pages-fix.patch nfs-enable-swap-on-nfs-fix.patch memcg-prevent-oom-with-too-many-dirty-pages.patch memcg-further-prevent-oom-with-too-many-dirty-pages.patch memcg-add-mem_cgroup_from_css-helper-fix-2.patch linux-next.patch rbtree-performance-and-correctness-test-fix.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html