From: Adam Baker <linux@baker-net.org.uk>
To: Andrew Lunn <andrew@lunn.ch>, Pawel Dembicki <paweldembicki@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Gregory Clement <gregory.clement@bootlin.com>,
Tony Dinh <mibodhi@gmail.com>
Subject: Re: [PATCH] ARM: dts: kirkwood: Add Zyxel NSA310S board
Date: Sat, 29 Oct 2022 01:14:52 +0100 [thread overview]
Message-ID: <e78b6ece-8dfa-733f-d449-1108a9545223@baker-net.org.uk> (raw)
In-Reply-To: <YzWVOyM+Z3AFSI7c@lunn.ch>
On 29/09/2022 13:53, Andrew Lunn wrote:
>> +// SPDX-License-Identifier: GPL-2.0-only
> Same license comment. However, you can only change the license if it
> is your code. If you did the conversion from a board setup file to DT,
> you can change the license. If somebody else did that and you are just
> submitting it, then we need to keep to GPL-2.0-only.
As it lists my name in the copyright I'm guessing it is derived from my
nsa320 device tree. If so I have no objection to relicensing to GPL2 +
MIT for anything that came from my code. It is different enough I don't
think I could reasonably lay claim to it anyway. It looks as though some
of it such as the keys section came from the earlier nsa310 device tree
rather than mine. That looks like Andrew Lunn's clean up of it rather
than Tero Jaasko's original.
There is no temperature or fan monitoring listed in the device tree, do
you know if the 310s supports it and if so what sensor it uses?
Adam Baker
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-29 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:01 [PATCH] ARM: dts: kirkwood: Add Zyxel NSA310S board Pawel Dembicki
2022-09-29 12:53 ` Andrew Lunn
2022-10-29 0:14 ` Adam Baker [this message]
2022-10-29 0:49 ` Tony Dinh
2022-10-29 14:31 ` Andrew Lunn
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=e78b6ece-8dfa-733f-d449-1108a9545223@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mibodhi@gmail.com \
--cc=paweldembicki@gmail.com \
/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).