On Sun, Oct 22, 2017 at 9:09 PM, Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> wrote: > I would first implement doing everything in a single binary and only > think about the complicated split in a "normal" and an "aggressive" > sparse binary if the overhead is too high and people start wailing. I think some thing like detect the ptrlist nest modify is on a hot path does not belong to release version of sparse. I usually will not wait until it has some performance problem. Chris -- 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
