linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor
Date: Wed, 23 Jun 2021 06:21:01 +0200	[thread overview]
Message-ID: <m3r1gt5hzm.fsf@t19.piap.pl> (raw)
In-Reply-To: <YNHQDNdpxcY8+IV2@pendragon.ideasonboard.com> (Laurent Pinchart's message of "Tue, 22 Jun 2021 14:57:00 +0300")

Laurent Pinchart <laurent.pinchart@ideasonboard.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

  reply	other threads:[~2021-06-23  4:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 11:18 [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor Krzysztof Hałasa
2021-06-22 11:57 ` Laurent Pinchart
2021-06-23  4:21   ` Krzysztof Hałasa [this message]
2021-06-23  4:31     ` Laurent Pinchart
2021-06-23  5:28       ` Krzysztof Hałasa
2021-06-23 13:17         ` Laurent Pinchart
2021-06-23 14:27           ` Kieran Bingham
2021-06-24  4:57             ` Krzysztof Hałasa
2021-06-24 12:10               ` Laurent Pinchart
2021-06-24 12:39                 ` Greg KH
2021-06-24 13:22                   ` Krzysztof Hałasa
2021-06-24 13:29                     ` Greg KH
2021-06-24 14:17                       ` Krzysztof Hałasa
2021-06-24 14:31                         ` Greg KH
2021-06-24 13:34                     ` Laurent Pinchart
2021-06-24 14:42                       ` Greg KH
2021-06-25  6:03                         ` Krzysztof Hałasa
2021-06-25  6:59                           ` Greg KH
2021-06-24 11:10   ` Mauro Carvalho Chehab
2021-06-24 13:51     ` Krzysztof Hałasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3r1gt5hzm.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).