On 27 February 2018 at 22:04, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > On 25 February 2018 at 20:18, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: >>>> 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. >> > > Hi Chris, one of the patch sets I need are the ones where Luc added > type to several Sparse OP codes. These are in the series: > > https://marc.info/?l=linux-sparse&m=149063626507168&w=2 > > I don't think Luc is able to resubmit these - are you able to apply > them somehow? These contain the OP_PUSH patch which you will need to > omit. > BTW you could apply these to a branch (suggest llvm-fixes?) - at least that way I can work against that branch without impacting anything else. Thanks and 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
