On Wed, Aug 2, 2017 at 9:47 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > I have merge Luc's fix-fuzzy-crashes-v3 into sparse-next as base. > > I also revert the change aa497b9f6dab68a1f1d2b8f02bc03b523de15716 > which revert commit 11b1a83b d7985338. > > In other words, 11b1a83b d7985338 is reinstated in sparse-next. > Only the test case has remain in the sparse-next. > > I want to give Luc's 7 patches a bit more chance to test. That is what > sparse-next was for, testing new patches. > > I think it is a better base for the RC5 any way. > > I have verify the full kernel checking with spase remain pretty much unchanged. > More testing on the way. Guys, please throw more test on the sparse-next as > well. > > Please report back if any one run into problem with the current tip of > sparse-next. > > BTW, Luc, if you have better patch to fix the second nested loop delete > problem, feel free to trash the one in sparse-next :-) Which patch? Which second nested loop delete? The "Let pseudo->users loop on duplicate version of list" one? -- 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
