On Wed, Jul 19, 2017 at 02:16:54PM -0700, Christopher Li wrote: > On Wed, Jul 19, 2017 at 4:43 PM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > > > I'm not yet fully back but I'll be able to look at it later, probably > > tomorrow (it's already evening here). > > That is fine. How about we temporary disable that in the 0.5.1 release. > Re-enable it with some proper fix of the phi domination problem. e.g. > 0.5.2. > > Right now I feel a little bit uncomfortable with 11b1a83b. Already two bugs > trigger in the field. The previous fix d7985338 is not a proper fix any way. > I think the right thing to do is just release 0.5.1 with 11b1a83b disabled. > Turn on 11b1a83b in sparse-next and do more fixing there. Release > 0.5.2 when it settle down with other new merges. I can't run all the validation I had done for -rc4 but I have no objections about the revert (I'm pretty sure there will be some side-effects though). -- 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
