From: Greg KH <gregkh@linuxfoundation.org>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
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: Thu, 24 Jun 2021 15:29:13 +0200 [thread overview]
Message-ID: <YNSIqSQeefzai4fW@kroah.com> (raw)
In-Reply-To: <m3wnqj4ct3.fsf@t19.piap.pl>
On Thu, Jun 24, 2021 at 03:22:48PM +0200, Krzysztof Hałasa wrote:
> Hi Greg,
>
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> > +// SPDX-License-Identifier: GPL-2.0
>
> > Putting the above line on a file _IS_ a legal declaration that the file
> > is released under GPL-2.0. It's pretty simple :)
>
> Do you think putting this line anywhere, in any file, does it?
Yes.
> That would be crazy.
Nope, that's how license declarations work. Please discuss this with a
lawyer if you are confused.
> How about a book, e.g. describing a patch submission process (but not
> a copy of kernel's Documentation). The same?
That does not make sense, please explain.
> Also - in all countries? Most of them?
Yes.
> Come on.
>
> Then why would we need the Signed-off-by?
S-o-b is a DIFFERENT thing entirely. Please go read the DCO for what
you are agreeing to there, it is a declaration for what you are doing.
> From my perspective, the SPDX-License-Identifier is only meaningful when
> the file is actually a part of the kernel, or if, at least, it's been
> presented for merge, with Signed-off-by etc.
Not true at all, sorry. Same for a Copyright line. Again, if you have
questions about this, please contact your company lawyer, they will be
glad to explain it in detail to you.
greg k-h
next prev parent reply other threads:[~2021-06-24 13:29 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
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 [this message]
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=YNSIqSQeefzai4fW@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=khalasa@piap.pl \
--cc=kieran.bingham@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.