linux-kernel - Re: [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m3r1gt5hzm.fsf@t19.piap.pl>
Date:   Wed, 23 Jun 2021 06:21:01 +0200
From:   Krzysztof Hałasa <khalasa@...p.pl>
To:     Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor

Laurent Pinchart <laurent.pinchart@...asonboard.com> 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.
-- 
Krzysztof Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa