On Fri, Nov 18, 2016 at 12:13:58AM +0800, Christopher Li wrote: > On Thu, Nov 3, 2016 at 5:45 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > Such situation may simply show that what was tested is now fixed > > and that it's juste the test annotation which need to be adapted, > > but can be a sign that something else is broken. > > > > Reporting the exact result (failure/success, known-to-fail/expect-to-succeed) > > make the testsuite more useful and allow to use more efficiently > > git-bisect or other automated testing tools. > > I like what you are doing as a result. > > But I think the implementation has room to improve. > I don't like deep and messy "else" statement. > > I attach a patch which I modify base on yours. I hope it is > easier to read. Care to review it? Yes, I much prefer like this. Thanks. But there is something I would like to check but I can't do that now. I'll come back on it later. Luc -- 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
