2018-02-16 6:07 GMT+09:00 Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>: > Currently, sparse issues warnings on code using an attribute > it doesn't know about. > > One of the problem with this is that these warnings have no > value for the developer, it's just noise for him. At best these > warnings tell something about some deficiencies of sparse itself > but not about a potential problem with code analyzed. > > A second problem with this is that sparse release are, alas, > less frequent than new attributes are added to GCC. > > So, avoid the noise by asking sparse to not warn about > attributes it doesn't know about. > > Reference: https://marc.info/?l=linux-sparse&m=151871600016790 > Reference: https://marc.info/?l=linux-sparse&m=151871725417322 > Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> > --- > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Applied to linux-kbuild/kbuild. Thanks! -- Best Regards Masahiro Yamada -- 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
