All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pankaj Bansal <pankaj.bansal@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Stephen Warren <swarren@nvidia.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>, Varun Sethi <V.Sethi@nxp.com>,
	Udit Kumar <udit.kumar@nxp.com>, Leo Li <leoyang.li@nxp.com>
Subject: Re: using interrupt controller dt-bindings macros in Non GPL dts files
Date: Mon, 22 Oct 2018 11:34:26 +0100	[thread overview]
Message-ID: <20181022103426.GA4546@kroah.com> (raw)
In-Reply-To: <HE1PR0402MB3323E108AF8810DEC38B7691F1F40@HE1PR0402MB3323.eurprd04.prod.outlook.com>

On Mon, Oct 22, 2018 at 09:18:02AM +0000, Pankaj Bansal wrote:
> 2. Would it be possible for the copyright owners of these header files
> to make these files dual licensed, so that we are able to use these
> files in our dts/dtsi files?

You are going to have to deal with the legal departments of the
companies that own those copyrights.  Again, talk to your legal
department about how that would even work, or if they even wish for you
to be asking people and companies to do that.

good luck!

greg k-h

  reply	other threads:[~2018-10-22 10:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22  3:48 using interrupt controller dt-bindings macros in Non GPL dts files Pankaj Bansal
2018-10-22  3:56 ` Pankaj Bansal
2018-10-22  8:29 ` Greg Kroah-Hartman
2018-10-22  9:18   ` Pankaj Bansal
2018-10-22 10:34     ` Greg Kroah-Hartman [this message]
2018-10-23 19:10       ` Li Yang
2018-10-23 19:39         ` Stephen Warren
2018-10-23 21:39           ` Stephen Warren
2018-10-23 22:31             ` Li Yang
2018-10-24  9:27             ` Geert Uytterhoeven

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=20181022103426.GA4546@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=V.Sethi@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=leoyang.li@nxp.com \
    --cc=mark.rutland@arm.com \
    --cc=pankaj.bansal@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=swarren@nvidia.com \
    --cc=udit.kumar@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.