The patch titled Subject: regmap: cope with bitops API change (for_each_set_bit_cont) has been added to the -mm tree. Its filename is bitops-remove-for_each_set_bit_cont-fix.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Subject: regmap: cope with bitops API change (for_each_set_bit_cont) Signed-off-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Cc: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> Cc: Akinobu Mita <akinobu.mita@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/base/regmap/regcache-lzo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/base/regmap/regcache-lzo.c~bitops-remove-for_each_set_bit_cont-fix drivers/base/regmap/regcache-lzo.c --- a/drivers/base/regmap/regcache-lzo.c~bitops-remove-for_each_set_bit_cont-fix +++ a/drivers/base/regmap/regcache-lzo.c @@ -341,7 +341,7 @@ static int regcache_lzo_sync(struct regm lzo_blocks = map->cache; i = min; - for_each_set_bit_cont(i, lzo_blocks[0]->sync_bmp, + for_each_set_bit_from(i, lzo_blocks[0]->sync_bmp, lzo_blocks[0]->sync_bmp_nbits) { if (i > max) continue; _ Subject: Subject: regmap: cope with bitops API change (for_each_set_bit_cont) Patches currently in -mm which might be from sfr@xxxxxxxxxxxxxxxx are linux-next.patch x86-use-this_cpu_xxx-to-replace-percpu_xxx-funcs.patch bitops-remove-for_each_set_bit_cont-fix.patch syscalls-x86-add-__nr_kcmp-syscall-v8-fix.patch syscalls-x86-add-__nr_kcmp-syscall-v8-fix-2.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