On Thu, Aug 10, 2017 at 8:01 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Sun, Mar 12, 2017 at 9:13 PM, Dibyendu Majumdar wrote: > > For those test case. I think it is very welcome to integrate into sparse. Sure. Very welcome. > If you want, you can break them down to smaller, digestible piece > and start submitting to sparse as patch series for review, or git pull > request. It will not get pull into this release v0.5.1 for sure. We can > start the discussion now. I can even have a post release branch doing > the merges for the patches after the release. > >> These are not exactly in the format currently used for testing sparse. >> It will be nice however to add all the test cases to the official >> sparse repository. > > That is fine. If it is all just test cases, that is relative safe. > Luc has a hue pile of pending patches I want to merge. If you touch > some of those core components, which result in Luc need to fix up > his repository a lot, then I would say hold a little bit for Luc's patches > being merged. The test case should be more or less fine. Yes, in no ways should additional test cases be a problem. -- 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
