From: Greg KH <gregkh@linuxfoundation.org>
To: Valentina Manea <valentina@rosedu.org>
Cc: "Linux Kernel Community @ ROSEdu" <firefly@lists.rosedu.org>,
devel@driverdev.osuosl.org, shuah.kh@samsung.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
ly80toro@cip.cs.fau.de, tobias.polzer@fau.de,
dominik.paulus@fau.de, ihadzic@research.bell-labs.com
Subject: Re: [firefly] [PATCH 06/12] staging: usbip: userspace: add new list API
Date: Thu, 6 Mar 2014 11:55:27 -0800 [thread overview]
Message-ID: <20140306195527.GC3403@kroah.com> (raw)
In-Reply-To: <CAByK=5bzS4R0sGj5w5x8gc8DcKXvnr58WskoShuq6G30YTsOgQ@mail.gmail.com>
On Thu, Mar 06, 2014 at 07:45:27AM +0200, Valentina Manea wrote:
>
>
>
> On Wed, Mar 5, 2014 at 12:16 PM, Dan Carpenter <dan.carpenter@oracle.com>
> wrote:
>
> On Tue, Mar 04, 2014 at 10:35:39PM -0800, Greg KH wrote:
> > On Tue, Mar 04, 2014 at 09:10:46PM +0200, Valentina Manea wrote:
> > > Add a new list API from CCAN.
> >
> > Why can't you just take the one from the kernel, as userspace is GPLv2
> > code, right?
> >
> > And are you sure CC0 is a "valid" license that you can mix with GPLv2
> > code? I ask this seriously, as I have heard that CC0 really isn't even
> > a valid license at all, and if I was to accept this patch, I'm going to
> > have to go talk to some lawyers, which isn't going to be fun...
> >
>
> GNU people say it's compitable.
> https://www.gnu.org/licenses/license-list.html#CC0
>
> It's not a good license because it doesn't say anything about that there
> is no warranties. Maybe other reasons as well.
>
> regards,
> dan carpenter
>
>
>
> As Dan pointed out, it seems that CC0 is compatible with GPLv2.
> However, if needed, I can change the lists API.
You only need the list.h file from the kernel source, strip it down to
just the functions you actually use, and then you should be fine. Much
smaller codebase to worry about as well, which is always good.
Just be explicit where you copied the file from.
thanks,
greg k-h
next prev parent reply other threads:[~2014-03-06 19:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 19:10 [PATCH 00/12] Migrate usbip-utils to libudev Valentina Manea
2014-03-04 19:10 ` [PATCH 01/12] staging: usbip: userspace: migrate usbip_bind " Valentina Manea
2014-03-05 9:42 ` Dan Carpenter
2014-03-05 10:15 ` Dan Carpenter
2014-03-06 6:17 ` Valentina Manea
2014-03-05 9:56 ` Dan Carpenter
2014-03-06 16:15 ` Shuah Khan
2014-03-06 18:19 ` Dan Carpenter
2014-03-04 19:10 ` [PATCH 02/12] staging: usbip: userspace: remove useless libsysfs includes Valentina Manea
2014-03-04 19:10 ` [PATCH 03/12] staging: usbip: userspace: migrate usbip_unbind to libudev Valentina Manea
2014-03-06 16:31 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 04/12] staging: usbip: userspace: migrate usbip_list " Valentina Manea
2014-03-06 20:57 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 05/12] staging: usbip: userspace: re-add interface information listing Valentina Manea
2014-03-06 21:11 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 06/12] staging: usbip: userspace: add new list API Valentina Manea
2014-03-05 6:35 ` Greg KH
2014-03-05 10:16 ` Dan Carpenter
[not found] ` <CAByK=5bzS4R0sGj5w5x8gc8DcKXvnr58WskoShuq6G30YTsOgQ@mail.gmail.com>
2014-03-06 19:55 ` Greg KH [this message]
2014-03-04 19:10 ` [PATCH 07/12] staging: usbip: userspace: move sysfs_utils to libsrc Valentina Manea
2014-03-04 19:10 ` [PATCH 08/12] staging: usbip: userspace: migrate usbip_host_driver to libudev Valentina Manea
2014-03-06 21:43 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 09/12] staging: usbip: userspace: remove class device infrastructure in vhci_driver Valentina Manea
2014-03-06 21:59 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 10/12] staging: usbip: userspace: migrate vhci_driver to libudev Valentina Manea
2014-03-06 22:07 ` Shuah Khan
2014-03-04 19:10 ` [PATCH 11/12] staging: usbip: userspace: remove libsysfs flag and autoconf check Valentina Manea
2014-03-04 19:10 ` [PATCH 12/12] staging: usbip: userspace: update dependencies in README Valentina Manea
2014-03-05 6:37 ` [PATCH 00/12] Migrate usbip-utils to libudev Greg KH
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=20140306195527.GC3403@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dominik.paulus@fau.de \
--cc=firefly@lists.rosedu.org \
--cc=ihadzic@research.bell-labs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ly80toro@cip.cs.fau.de \
--cc=shuah.kh@samsung.com \
--cc=tobias.polzer@fau.de \
--cc=valentina@rosedu.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).