On Thu, Feb 12, 2015 at 07:23:11PM +0100, Arturo Borrero Gonzalez wrote: > >> net/netfilter/nft_compat.c:140:37: sparse: incorrect type in assignment (different base types) > net/netfilter/nft_compat.c:140:37: expected restricted __be16 [usertype] ethproto > net/netfilter/nft_compat.c:140:37: got unsigned char [unsigned] [usertype] proto > >> net/netfilter/nft_compat.c:351:37: sparse: incorrect type in assignment (different base types) > net/netfilter/nft_compat.c:351:37: expected restricted __be16 [usertype] ethproto > net/netfilter/nft_compat.c:351:37: got unsigned char [unsigned] [usertype] proto Please, reword the title and resubmit. Basically, sparse has discovered a real bug. I'm telling this because we cannot pass patch to calm down sparse warnings to the 'net' tree and I would like to make sure that people understand that this is fixing a breakage in ebtables-compat, so it should follow the fast path to mainstream. Thanks. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
