From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] ARM: dts: berlin2cd: add Valve Steam Link board
Date: Wed, 14 Mar 2018 15:43:23 +0800 [thread overview]
Message-ID: <20180314154323.184cf435@xhacker.debian> (raw)
In-Reply-To: <alpine.LNX.2.20.13.1803141013040.21514@monopod.intra.ispras.ru>
On Wed, 14 Mar 2018 10:22:11 +0300 Alexander Monakov wrote:
> On Wed, 14 Mar 2018, Jisheng Zhang wrote:
>
> > > +/*
> > > + * Copyright 2018 Alexander Monakov <amonakov@gmail.com>
> > > + *
> > > + * SPDX-License-Identifier: (GPL-2.0 OR MIT)
> >
> > Mind to license it under GPL2 or X11?
>
> MIT is the same as X11 but without the references to the X Consortium that
> do not make sense in the kernel context: please see [1] and [2]. The MIT
> license is present under LICENSES/preferred in the kernel tree, but not the
> X11 license.
Understood.
>
> The berlin2cd.dtsi file first says "the X11 license", but then the actual
> license text appearing in the file is the MIT license.
Yes, I'll send patches to add SPDX tags to all berlin SoC dtsi and s/X11/MIT.
Thanks for pointing this out.
>
> [1] https://spdx.org/licenses/MIT.html
> [2] https://spdx.org/licenses/X11.html
>
> > Other source usually tag as:
> > // SPDX-License-Identifier: (GPL-2.0 OR X11)
> >
> > And the tag is put into the first line, could we keep the style?
>
> Right. With the clarification regarding X11/MIT above, I'll change to
>
> // SPDX-License-Identifier: GPL-2.0 OR MIT
> // Copyright 2018 Alexander Monakov <amonakov@gmail.com>
>
> Is that okay?
Yes, it's OK.
next prev parent reply other threads:[~2018-03-14 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 16:00 [PATCH 0/8] Refresh Marvell BG2CD SoC support Alexander Monakov
2018-03-11 16:00 ` [PATCH 1/8] ARM: berlin: extend BG2CD Kconfig entry Alexander Monakov
2018-03-14 5:58 ` Jisheng Zhang
2018-03-14 7:05 ` Alexander Monakov
2018-03-18 17:11 ` [PATCHv2 " Alexander Monakov
2018-03-11 16:00 ` [PATCH 2/8] ARM: dts: berlin2cd: fix local timer interrupt flags Alexander Monakov
2018-03-11 16:00 ` [PATCH 3/8] ARM: dts: berlin2cd: move PMU node from soc to root Alexander Monakov
2018-03-11 16:00 ` [PATCH 4/8] ARM: dts: berlin2cd: add ADC/thermal sensor node Alexander Monakov
2018-03-11 16:00 ` [PATCH 5/8] ARM: dts: berlin2cd: add remaining Cortex-A9 nodes Alexander Monakov
2018-03-11 16:00 ` [PATCH 6/8] ARM: dts: berlin2cd: add remaining nodes to apb subtrees Alexander Monakov
2018-03-11 16:00 ` [PATCH 7/8] ARM: dts: berlin2cd: add a label for the CPU node Alexander Monakov
2018-03-11 16:00 ` [PATCH 8/8] ARM: dts: berlin2cd: add Valve Steam Link board Alexander Monakov
2018-03-14 6:23 ` Jisheng Zhang
2018-03-14 7:22 ` Alexander Monakov
2018-03-14 7:43 ` Jisheng Zhang [this message]
2018-03-14 8:28 ` Jisheng Zhang
2018-03-18 17:12 ` [PATCHv2 " Alexander Monakov
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=20180314154323.184cf435@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=linux-arm-kernel@lists.infradead.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).