Hi Krzysztof, On Wed, Jun 23, 2021 at 06:21:01AM +0200, Krzysztof Hałasa wrote: > Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> writes: > > > To spend time reviewing this code, I want to know it will be mergeable, > > and that requires a SoB line. That's a blocker I'm afraid. > > So how do you propose to solve the situation, in which my driver is > rejected, but another persor takes it, makes changes (btw breaking it), > and presents it as their own, and it's accepted? This is a paid work and > I'm required to put in my employer's copyright over the code. > I could have made this error once - but no more. > > The code will be mergeable, as I already wrote. Why would I bother > otherwise? But I cannot let that history to repeat itself. How does a lack of an SoB line prevent someone from doing exactly what you've described above ? Maintainers usually understand these issues. They may fail to notice, but if you point out a patch that would steal your work, that would prevent it from being merged. -- Regards, Laurent Pinchart