From: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: DTML <devicetree@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>, SoC Team <soc@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
Paul Murphy <paul.j.murphy@intel.com>,
Will Deacon <will@kernel.org>,
Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/5] Add initial Keem Bay SoC / Board support
Date: Tue, 14 Jul 2020 14:33:44 +0100 [thread overview]
Message-ID: <445bb8712b57edb02e776bc47a1350c43f37efff.camel@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a3GVZftAZKEHC3TjDRL86vYOkND6TNuVq1KjssOHi5AXw@mail.gmail.com>
On Tue, 2020-07-14 at 14:40 +0200, Arnd Bergmann wrote:
> On Wed, Jul 8, 2020 at 7:50 PM Daniele Alessandrelli
> <daniele.alessandrelli@linux.intel.com> wrote:
> > Hi,
> >
> > This patch-set adds initial support for a new Intel Movidius SoC
> > code-named
> > Keem Bay. The SoC couples an ARM Cortex A53 CPU with an Intel
> > Movidius VPU.
> >
> > This initial patch-set enables only the minimal set of components
> > required
> > to make the Keem Bay EVM board boot into initramfs.
> >
> > Changes from v1 to v2:
> > * Moved keembay-scmi-mailbox driver to a separate patchset
> > * Removed Keem Bay SCMI mailbox and SCMI node from Keem Bay SoC
> > device tree
>
> This all looks basically ok, but I noticed that the DT bindings ands
> DTS files all have a
> "GPL-2.0-only" tag. Usually we make those dual-licensed in order to
> make it easier
> to distribute them with a non-GPL bootloader and synchronize them
> between
> projects.
>
> Do you know if the GPL-2.0-only part was picked intentionally, or if
> it can
> be changed to dual-licensed?
Thanks for reviewing the patchset. I'll change those files to dual-
licensed and re-submit.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-14 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 17:50 [PATCH v2 0/5] Add initial Keem Bay SoC / Board support Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 1/5] arm64: Add config for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 2/5] dt-bindings: arm: Add Keem Bay bindings Daniele Alessandrelli
2020-07-14 3:12 ` Rob Herring
2020-07-14 13:29 ` Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 3/5] MAINTAINERS: Add maintainers for Keem Bay SoC Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 4/5] arm64: dts: keembay: Add device tree " Daniele Alessandrelli
2020-07-08 17:50 ` [PATCH v2 5/5] arm64: dts: keembay: Add device tree for Keem Bay EVM board Daniele Alessandrelli
2020-07-14 12:40 ` [PATCH v2 0/5] Add initial Keem Bay SoC / Board support Arnd Bergmann
2020-07-14 13:33 ` Daniele Alessandrelli [this message]
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=445bb8712b57edb02e776bc47a1350c43f37efff.camel@linux.intel.com \
--to=daniele.alessandrelli@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.j.murphy@intel.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).