From: Scott Wood <scottwood@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Meador Inge <meador_inge@mentor.com>,
openmcapi-dev@googlegroups.com,
devicetree-discuss@lists.ozlabs.org,
Hollis Blanchard <hollis_blanchard@mentor.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] powerpc: add support for MPIC message register API
Date: Fri, 17 Jun 2011 11:58:28 -0500 [thread overview]
Message-ID: <20110617115828.3cebd5c9@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <1308288784.32158.30.camel@pasglop>
On Fri, 17 Jun 2011 15:33:04 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2011-05-31 at 14:19 -0500, Meador Inge wrote:
> > +void mpic_msgr_enable(struct mpic_msgr *msgr)
> > +{
> > + out_be32(msgr->mer, in_be32(msgr->mer) | (1 << msgr->num));
> > +}
> > +EXPORT_SYMBOL(mpic_msgr_enable);
>=20
> Why are all those exported non-GPL ? We have a policy of making new
> in-kernel APIs generally GPL only.
=46rom Documentation/DocBook/kernel-hacking.tmpl:
<sect1 id=3D"sym-exportsymbols-gpl">
<title><function>EXPORT_SYMBOL_GPL()</function> =20
<filename class=3D"headerfile">include/linux/module.h</filename></title>
=20
<para> =20
Similar to <function>EXPORT_SYMBOL()</function> except that the
symbols exported by <function>EXPORT_SYMBOL_GPL()</function> can
only be seen by modules with a =20
<function>MODULE_LICENSE()</function> that specifies a GPL
compatible license. It implies that the function is considered
an internal implementation issue, and not really an interface.
</para> =20
</sect1>
When did this change from "considered an internal implementation issue, and
not really an interface" to "all new interfaces"?
-Scott
next prev parent reply other threads:[~2011-06-17 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:19 [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-05-31 19:19 ` [PATCH v3 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-05-31 19:23 ` Scott Wood
2011-06-02 14:33 ` Meador Inge
2011-05-31 19:19 ` [PATCH v3 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-06-17 5:33 ` Benjamin Herrenschmidt
2011-06-17 13:49 ` [openmcapi-dev] " Meador Inge
2011-06-17 16:58 ` Scott Wood [this message]
2011-06-17 22:58 ` Benjamin Herrenschmidt
2011-06-20 15:59 ` Scott Wood
2011-06-21 7:47 ` Benjamin Herrenschmidt
2011-06-30 3:04 ` [openmcapi-dev] " Meador Inge
2011-06-30 4:19 ` Benjamin Herrenschmidt
2011-06-09 14:44 ` [openmcapi-dev] [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
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=20110617115828.3cebd5c9@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hollis_blanchard@mentor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meador_inge@mentor.com \
--cc=openmcapi-dev@googlegroups.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;
as well as URLs for NNTP newsgroup(s).