All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Mike Waychison <mike@waychison.com>, Adrian Bunk <bunk@stusta.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6 patch] unexport complete_all
Date: Fri, 04 Mar 2005 12:55:09 +0000	[thread overview]
Message-ID: <1109940906.26799.20.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0503040240314120ea@mail.gmail.com>

> Andrew, what is the policy for adding exports for out of tree GPL code?
> 
> IMHO although it is convenient for maintainers of such code it is
> inconvenient for us (ie. when making changes to code) and gives
> people false assumptions about stability of *in-kernel* APIs.

Why isn't it _GPL if it is for a specific module need ?

Even more so for those cases where a person adds a non _GPL export for
another persons code. 

  parent reply	other threads:[~2005-03-04 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04  8:09 [2.6 patch] unexport complete_all Mike Waychison
2005-03-04 10:40 ` Bartlomiej Zolnierkiewicz
2005-03-04 11:07   ` Adrian Bunk
2005-03-04 17:08     ` mike
2005-03-04 20:41       ` Adrian Bunk
2005-03-04 11:15   ` Andrew Morton
2005-03-04 13:14     ` Bartlomiej Zolnierkiewicz
2005-03-08  8:24       ` Bartlomiej Zolnierkiewicz
2005-03-04 13:18     ` Adrian Bunk
2005-03-04 12:55   ` Alan Cox [this message]
2005-03-04 11:05 ` Adrian Bunk
2005-03-04 16:58   ` mike
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04  0:47 Adrian Bunk

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=1109940906.26799.20.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@waychison.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.