On Sun, Feb 25, 2018 at 11:34 AM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > Hi, > > I have a bunch of LLVM fixes in my project that is derived from > Sparse. These fixes are more comprehensive than the fixes posted in > this list - although in some cases they are derived from fixes posted > here. > > I would like to submit the LLVM fixes from my repository - I am happy > to back port them to Sparse. Sure, very welcome. > In some ways it is easier to post a single patch for sparse-llvm.c > that contains all the fixes - as then it can applied or removed easily > as a single change. Or I can post smaller patches if that is the > preferred approach. It would be best to separate the patch you depend on vs your own patches. How big is your change? If you have a link I can take a look. > In some cases there are patches that are based on ones posted here by > Luc - so I am not sure how to get these across with the correct > attribution. The best solution would be have Luc send small git merge request for the LLVM patch you are depend on. Merge those first. Failing that. I can apply sparse patch from patchworks as well. It just more work for every one to go through that route. 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
