On 25 February 2018 at 19:56, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Sun, Feb 25, 2018 at 11:34 AM, Dibyendu Majumdar >> 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. > I don't have one yet - I will need to prepare this as my version cannot be directly applied to Sparse. > >> 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. > Okay I will identify the specific patches I need. I will try to play them in my copy / and try to then apply my changes on top. Hopefully this way I can send patches that can be merged. Regards Dibyendu -- 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
