All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Juan David Gonzalez Cobas <juan.david.gonzalez.cobas@cern.ch>
Cc: Alessandro Rubini <rubini@gnudd.com>,
	linux-kernel@vger.kernel.org, cota@braap.org,
	siglesias@igalia.com, rob@landley.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/8] FMC: add core bus driver
Date: Tue, 18 Jun 2013 10:40:47 -0700	[thread overview]
Message-ID: <20130618174047.GA21738@kroah.com> (raw)
In-Reply-To: <CADDK0KdrVgmXN-TZw8E43JRNk5Wb_cfM6pUWaSxbJ49GU72cTg@mail.gmail.com>

On Tue, Jun 18, 2013 at 09:30:00AM +0200, Juan David Gonzalez Cobas wrote:
> Hi all,
> 
> On Tue, Jun 18, 2013 at 1:38 AM, Alessandro Rubini <rubini@gnudd.com> wrote:
> 
>     [...]
> 
>  
> 
>     Yes, it was intended. I don't think it's an issue for merging, but
>     I understand you've seen so many such undesired copy-paste errors.
> 
> 
> CERN policies favour GPLv3 as default open source license as a recommendation.
> The "GPLv2 or later" is, in effect, intentional.

Ok, thanks for verifying this.

>     >> +EXPORT_SYMBOL(fmc_driver_unregister);
>     >
>     > Any specific reason these aren't EXPORT_SYMBOL_GPL()?
>     >
>     > Again, just have to ask.
> 
>     I think we want to allow for proprietary FMC drivers. I personally
>     don't feel this is a core kernel technology.  But I'll let David Cobas
>     expand on CERN policies, as I'm only a consultant.
> 
> 
> CERN policies (mostly recommendations) concern esp. the return of
> investment of taxpayer money to society. In view of the potential use
> cases of FMC, EXPORT_SYMBOL_GPL would better serve that
> purpose than merely allowing proprietary modules, so GPL exports
> are fine.

Great.

Alessandro, care to respin the patches that I didn't apply and resend
them so that I can?

thanks,

greg k-h

  parent reply	other threads:[~2013-06-18 17:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  7:13 [PATCH 0/8] Support for FMC carriers and mezzanines Alessandro Rubini
2013-06-12  7:13 ` [PATCH 1/8] FMC: create drivers/fmc and toplevel Kconfig question Alessandro Rubini
2013-06-17 23:17   ` Greg KH
2013-06-17 23:24     ` Alessandro Rubini
2013-06-17 23:35       ` Greg KH
2013-06-12  7:13 ` [PATCH 2/8] FMC: add needed headers Alessandro Rubini
2013-06-17 23:21   ` Greg KH
2013-06-17 23:29     ` Alessandro Rubini
2013-06-17 23:35       ` Greg KH
2013-06-19 10:49   ` Arnd Bergmann
2013-06-19 11:08     ` Alessandro Rubini
2013-06-12  7:13 ` [PATCH 3/8] FMC: add core bus driver Alessandro Rubini
2013-06-17 23:15   ` Greg KH
2013-06-17 23:16   ` Greg KH
2013-06-17 23:38     ` Alessandro Rubini
2013-06-18  8:36       ` Juan David Gonzalez Cobas
     [not found]       ` <CADDK0KdrVgmXN-TZw8E43JRNk5Wb_cfM6pUWaSxbJ49GU72cTg@mail.gmail.com>
2013-06-18 17:40         ` Greg KH [this message]
2013-06-18 19:52           ` Alessandro Rubini
2013-06-12  7:13 ` [PATCH 4/8] FMC: add documentation for the core Alessandro Rubini
2013-06-12  7:14 ` [PATCH 5/8] FMC: add a software carrier driver Alessandro Rubini
2013-06-17 23:19   ` Greg KH
2013-06-12  7:14 ` [PATCH 6/8] FMC: add a software mezzanine driver Alessandro Rubini
2013-06-17 23:20   ` Greg KH
2013-06-12  7:14 ` [PATCH 7/8] FMC: add a driver to write mezzanine EEPROM Alessandro Rubini
2013-06-12  7:14 ` [PATCH 8/8] FMC: add a char-device mezzanine driver Alessandro Rubini
  -- strict thread matches above, loose matches on Subject: below --
2013-02-21 18:13 [PATCH RFC 0/8] drivers/fmc: bus support for ANSI-VITA 57.1 Alessandro Rubini
2013-02-21 18:14 ` [PATCH 3/8] FMC: add core bus driver Alessandro Rubini
2013-03-15 19:17   ` 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=20130618174047.GA21738@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cota@braap.org \
    --cc=juan.david.gonzalez.cobas@cern.ch \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=rubini@gnudd.com \
    --cc=siglesias@igalia.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.