1y ago

I got robbed of my first kernel contribution

ariel-miculas.github.io How I got robbed of my first kernel contribution

Context Around a year and a half ago, I’ve asked my former company for some time to work on an issue that was impacting the debugging capabilities in our project: gdbserver couldn’t debug multithreaded applications running on a PowerPC32 architecture. The connection to the gdbserver was broken and ...

There is a discussion on Hacker News, but feel free to comment here as well.

Hacker News @lemmy.smeargle.fans bot @lemmy.smeargle.fans

BOT

1y ago

I got robbed of my first kernel contribution

ariel-miculas.github.io /How-I-got-robbed-of-my-first-kernel-contribution/

4 4

Programming @programming.dev kairos @programming.dev 1y ago

How I got robbed of my first kernel contribution

ariel-miculas.github.io /How-I-got-robbed-of-my-first-kernel-contribution/

49 50

1 comments

Dev investigates and submits patch for known issue affecting him

Maintainer implements different approach saying: "Rather than trying to make the TS_FPR() macro even more complicated to fix the bug, or add more macros, instead add a special-case for 32-bit kernels. This is more obvious and hopefully avoids a similar bug happening again in future."

Dev does not show any other correspondence with maintainer, but paraphrases maintainer as saying: "Sorry, I like my version better. If you want to be a Linux kernel contributor, here’s an issue you could fix."