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 16:31:16 +0200 [thread overview]
Message-ID: <YNSXNPLKwbb+5vS8@kroah.com> (raw)
In-Reply-To: <m3o8bv4a9z.fsf@t19.piap.pl>
On Thu, Jun 24, 2021 at 04:17:28PM +0200, Krzysztof Hałasa wrote:
> Greg,
>
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> >> 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.
>
> Why not? I can put such a text on a book (say, an e-book) as well.
Where would that text be and what would it mean?
> I'd say you're right with the absence of indication to the contrary -
> but if someone explicitly states something is not (e.g. yet) under GPL,
> then how one could say SPDX-something has legal precedence is beyound
> me.
It is identical to saying "this file is licensed under this specific
license". That is what a spdx line means, please read up on them if you
are curious.
> > 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.
>
> Well, that's my position.
That's not what a signed-off-by means, please do not try to make it
something it is not.
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-24 14:31 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
2021-06-24 14:17 ` Krzysztof Hałasa
2021-06-24 14:31 ` Greg KH [this message]
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=YNSXNPLKwbb+5vS8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox