On 01/06/17 21:27, Luc Van Oostenryck 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 unconvenient or to allow to configure its limit. > > > The series can also be found on the tree: > git://github.com/lucvoo/sparse.git memcpy-max-count Heh, I think you know I wrote a similar patch about a decade ago ... [I tried to find it the other day but couldn't find it - I think it is on my old laptop, which doesn't get booted up these days!] ATB, Ramsay Jones -- 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
