On 09/25/14 at 08:10pm, Christopher Li wrote: > No, this test case is some thing gcc can handle and sparse > can't. Instead of patching the test result, we need to fix sparse > to handle it correctly. > > It is an open bug of sparse. OK. This was not clear from the commit message. Thanks for clarifying. -- 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
