On Fri, Jun 14, 2019 at 10:16:53PM -0700, Alexei Starovoitov wrote: > On Fri, Jun 14, 2019 at 9:27 PM Josh Poimboeuf <jpoimboe@xxxxxxxxxx> wrote: > > > > On Fri, Jun 14, 2019 at 05:02:36PM -0700, Alexei Starovoitov wrote: > > > On Fri, Jun 14, 2019 at 4:54 PM Josh Poimboeuf <jpoimboe@xxxxxxxxxx> wrote: > > > > The previous patch you posted has my patch description, push/pop and > > > > comment changes, with no credit: > > > > > > > > https://lkml.kernel.org/r/20190614210555.q4ictql3tzzjio4r@xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > > > > I'm sorry for reusing one sentence from your commit log and > > > not realizing you want credit for that. > > > Will not happen again. > > > > Um. What are you talking about? The entire patch was clearly derived > > from mine. Not just "one sentence from your commit log". The title, > > the pushes/pops in the prologue/epilogue, the removal of the > > "ebpf_from_cbpf" argument, the code spacing, and some of the non trivial > > comment changes were the same. > > > > > I also suggest you never touch anything bpf related. > > > Just to avoid this credit claims and threads like this one. > > > > Wth. I made a simple request for credit. Anybody can see the patch was > > derived from mine. It's not like I really care. It's just basic human > > decency. > > derived? do you really think so ? > Please fix your orc stuff that is still broken. > Human decency is fixing stuff that you're responsible for. > Your commit d15d356887e7 on April 23 broke stack traces. > And we reported it 3 weeks ago. > Yet instead of fixing it you kept arguing about JIT frame pointers > that is orthogonal issue and was in this state for the last 2 years. Again you're not making sense. The fix has already been posted. That was the point of this patch set. It's your call if you want to cherry pick the FP fix (which is a dependency of the ORC fix) without taking the others. -- Josh
