From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor
Date: Thu, 24 Jun 2021 15:10:34 +0300 [thread overview]
Message-ID: <YNR2OkXL+wUaKuy4@pendragon.ideasonboard.com> (raw)
In-Reply-To: <m3bl7v6er0.fsf@t19.piap.pl>
Hi Krzysztof,
CC'ing Greg to get his expert opinion on the topic.
On Thu, Jun 24, 2021 at 06:57:55AM +0200, Krzysztof Hałasa wrote:
> Hi Kieran, and others,
>
> Kieran Bingham <kieran.bingham@ideasonboard.com> writes:
>
> >>> The work is not published under GPL.
> >
> > This seems like an odd thing to say when your patch explicitly contains:
> >
> >> +++ b/drivers/media/i2c/ar0521.c
> >> @@ -0,0 +1,1060 @@
> >> +// SPDX-License-Identifier: GPL-2.0
>
> Such tags have meaning only in the kernel context, when signed-off etc.
> Alone, they aren't legal statements, especially when I explicitly state
> that it's not signed-off-by me yet. Nevertheless...
>
> Obviously, this code was always meant to be GPLed and it seems really
> crazy to me that we even have to have such conversations - about
> a non issue, at least from my POV.
>
> The fact is that 6 years ago I wrote driver for a SDTV frame grabber -
> and another developer "took" the development from me, and published as
> his own. This wasn't probably illegal - after all my driver was covered
> by the GPL from the start. But was it really how we all want things to
> work in Linux? With such experience, is anybody surprised I want to
> avoid this history repeating itself?
>
> For other patches I don't care about such formalities, but this driver
> is a work paid by an external entity and it would be unfortunate to
> end up the same way as the tw686x driver.
>
>
> I stated multiple times I will sign this code off when it's accepted.
> Is it really a problem? Really?
>
> If so... perhaps there is some other way?
>
> I'd hate to think that the next time I'm to keep my code unpublished.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2021-06-24 12:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 11:18 Krzysztof Hałasa
2021-06-22 11:57 ` Laurent Pinchart
2021-06-23 4:21 ` Krzysztof Hałasa
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 [this message]
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=YNR2OkXL+wUaKuy4@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=gregkh@linuxfoundation.org \
--cc=khalasa@piap.pl \
--cc=kieran.bingham@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
all inboxes | Powered by JetHome®