From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hyun Kwon <hyun.kwon@xilinx.com>
Cc: "Laura Abbott" <labbott@redhat.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <christian@brauner.io>,
devel@driverdev.osuosl.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
"Martijn Coenen" <maco@android.com>,
"Wendy Liang" <jliang@xilinx.com>,
"Michal Simek" <michal.simek@xilinx.com>,
"Cyril Chemparathy" <cyrilc@xilinx.com>
Subject: Re: [PATCH 1/1] staging: android: ion: Add the GPL exception for syscalls
Date: Thu, 14 Feb 2019 10:42:06 +0100 [thread overview]
Message-ID: <20190214094206.GB10895@kroah.com> (raw)
In-Reply-To: <1550102506-24731-2-git-send-email-hyun.kwon@xilinx.com>
On Wed, Feb 13, 2019 at 04:01:46PM -0800, Hyun Kwon wrote:
> Add "WITH Linux-syscall-note" to the license to not put GPL
> restrictions on user space programs using this header.
>
> Signed-off-by: Hyun Kwon <hyun.kwon@xilinx.com>
> ---
> drivers/staging/android/uapi/ion.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/android/uapi/ion.h b/drivers/staging/android/uapi/ion.h
> index 5d70098..46c93fc 100644
> --- a/drivers/staging/android/uapi/ion.h
> +++ b/drivers/staging/android/uapi/ion.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> /*
> * drivers/staging/android/uapi/ion.h
> *
> --
> 2.7.4
>
Yes, that is the correct thing to do, let me go queue this up.
thanks,
greg k-h
prev parent reply other threads:[~2019-02-14 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 0:01 [PATCH 0/1] staging: android: ion: add the GPL exception note to header Hyun Kwon
2019-02-14 0:01 ` [PATCH 1/1] staging: android: ion: Add the GPL exception for syscalls Hyun Kwon
2019-02-14 9:42 ` Greg Kroah-Hartman [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=20190214094206.GB10895@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=cyrilc@xilinx.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hyun.kwon@xilinx.com \
--cc=jliang@xilinx.com \
--cc=joel@joelfernandes.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=michal.simek@xilinx.com \
--cc=sumit.semwal@linaro.org \
--cc=tkjos@android.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
all inboxes | Powered by JetHome®