From: "Gross, Mark" <mark.gross@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"markgross@kernel.org" <markgross@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>, "bp@suse.de" <bp@suse.de>,
"damien.lemoal@wdc.com" <damien.lemoal@wdc.com>,
"dragan.cvetic@xilinx.com" <dragan.cvetic@xilinx.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"palmerdabbelt@google.com" <palmerdabbelt@google.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kelly, Seamus" <seamus.kelly@intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH v6 19/34] xlink-core: Add xlink core device tree bindings
Date: Tue, 20 Apr 2021 22:08:26 +0000 [thread overview]
Message-ID: <CY4PR11MB16703EA2D146854AEF3A94F68E489@CY4PR11MB1670.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9fb59639-3745-33e7-e89c-c9fb75e9c7c4@intel.com>
> -----Original Message-----
> From: Dave Hansen <dave.hansen@intel.com>
> Sent: Monday, April 12, 2021 2:33 PM
> To: mgross@linux.intel.com; markgross@kernel.org; arnd@arndb.de; bp@suse.de;
> damien.lemoal@wdc.com; dragan.cvetic@xilinx.com;
> gregkh@linuxfoundation.org; corbet@lwn.net; palmerdabbelt@google.com;
> paul.walmsley@sifive.com; peng.fan@nxp.com; robh+dt@kernel.org;
> shawnguo@kernel.org; jassisinghbrar@gmail.com
> Cc: linux-kernel@vger.kernel.org; Kelly, Seamus <seamus.kelly@intel.com>;
> devicetree@vger.kernel.org
> Subject: Re: [PATCH v6 19/34] xlink-core: Add xlink core device tree bindings
>
> On 2/12/21 2:22 PM, mgross@linux.intel.com wrote:
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) # Copyright (c)
> > +Intel Corporation. All rights reserved.
> > +%YAML 1.2
> > +---
> > +$id: "http://devicetree.org/schemas/misc/intel,keembay-xlink.yaml#"
> > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > +
> > +title: Intel Keem Bay xlink
>
> Is there a specific reason this is dual licensed? If so, can you please include
> information about the license choice in the next post's cover letter?
>
> If there is no specific reason for this contribution to be dual licensed, please make it
> GPL-2.0 only.
I will.
I'm just waiting on some testing before making the next post.
Thanks,
--mark
next prev parent reply other threads:[~2021-04-20 22:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210212222304.110194-1-mgross@linux.intel.com>
2021-02-12 22:22 ` [PATCH v6 02/34] dt-bindings: mailbox: Add Intel VPU IPC mailbox bindings mgross
2021-03-05 20:50 ` Rob Herring
2021-02-12 22:22 ` [PATCH v6 04/34] dt-bindings: Add bindings for Keem Bay IPC driver mgross
2021-03-05 21:01 ` Rob Herring
2021-03-08 20:20 ` mark gross
2021-04-12 21:24 ` Jassi Brar
2021-04-20 22:14 ` mark gross
2021-04-21 13:55 ` mark gross
2021-04-21 14:05 ` Jassi Brar
2021-04-21 15:29 ` Alessandrelli, Daniele
2021-02-12 22:22 ` [PATCH v6 06/34] dt-bindings: Add bindings for Keem Bay VPU " mgross
2021-02-12 22:22 ` [PATCH v6 17/34] xlink-ipc: Add xlink ipc device tree bindings mgross
2021-03-05 21:11 ` Rob Herring
2021-02-12 22:22 ` [PATCH v6 19/34] xlink-core: Add xlink core " mgross
2021-03-05 21:03 ` Rob Herring
2021-03-08 20:31 ` mark gross
2021-04-12 21:32 ` Dave Hansen
2021-04-20 22:08 ` Gross, Mark [this message]
2021-02-12 22:22 ` [PATCH v6 24/34] dt-bindings: misc: Add Keem Bay vpumgr mgross
2021-02-12 22:23 ` [PATCH v6 32/34] dt-bindings: misc: hddl_dev: Add hddl device management documentation mgross
2021-03-05 21:20 ` Rob Herring
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=CY4PR11MB16703EA2D146854AEF3A94F68E489@CY4PR11MB1670.namprd11.prod.outlook.com \
--to=mark.gross@intel.com \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=damien.lemoal@wdc.com \
--cc=dave.hansen@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mgross@linux.intel.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=seamus.kelly@intel.com \
--cc=shawnguo@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).