The patch titled Subject: lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned-fix has been removed from the -mm tree. Its filename was lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned-fix.patch This patch was dropped because it was folded into lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned.patch ------------------------------------------------------ From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> Subject: lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned-fix fix kerneldoc Cc: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx> Reported-by: Wu Fengguang <fengguang.wu@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- lib/bitmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN lib/bitmap.c~lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned-fix lib/bitmap.c --- a/lib/bitmap.c~lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned-fix +++ a/lib/bitmap.c @@ -1039,7 +1039,7 @@ EXPORT_SYMBOL(bitmap_onto); * @dst: resulting smaller bitmap * @orig: original larger bitmap * @sz: specified size - * @bits: number of bits in each of these bitmaps + * @nbits: number of bits in each of these bitmaps * * For each bit oldbit in @orig, set bit oldbit mod @sz in @dst. * Clear all other bits in @dst. See further the comment and _ Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are origin.patch mm-convert-p_mknonnuma-and-remaining-page-table-manipulations.patch fs-shrinker-always-scan-at-least-one-object-of-each-type.patch zram-rework-reset-and-destroy-path.patch task_mmu-add-user-space-support-for-resetting-mm-hiwater_rss-peak-rss.patch powerpc-add-running_clock-for-powerpc-to-prevent-spurious-softlockup-warnings.patch kernelh-remove-ancient-__function__-hack.patch lib-bitmap-update-bitmap_onto-to-unsigned.patch lib-bitmap-change-parameters-of-bitmap_fold-to-unsigned.patch hexdump-makes-it-return-amount-of-bytes-placed-in-buffer-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