On Sat, Jun 3, 2017 at 12:47 AM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > sparse will warn if memcpy() (and some others memcpy-like > functions) is called with a very large static byte count. > But this warning cannot be disabled and the limit is arbitrary > fixed at 100000. > > The goal of this series is to allow to disable this warning if > found too bothersome or to allow to configure its limit. > > > Changes since v1: > - take in account Ramsay's remarks and suggestion: > - fix some name mixups in the man page & commit message > - use a limit of 0 as being equivalent to an infinite > limit, effectively disabling the warning. > - somewhat rewrote the man page for -fmemcpy-max-count > - extend the limit's range > > The series can also be found on the tree: > git://github.com/lucvoo/sparse.git memcpy-max-count-v2 This V2 version of the series looks perfectly fine to me. Signed-off-By: Chris Li <sparse@xxxxxxxxxxx> Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
