mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel/module.c warning re: non-GPL modules looks wrong
Date: Sat, 9 Jun 2007 18:24:09 +0200	[thread overview]
Message-ID: <20070609162409.GB31493@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706090521250.28643@localhost.localdomain>

On Sat, Jun 09, 2007 at 05:25:08AM -0400, Robert P. J. Day wrote:
> 
>   from kernel/module.c:
> ...
>         ks = lookup_symbol(name, __start___ksymtab_gpl_future,
>                                  __stop___ksymtab_gpl_future);
>         if (ks) {
>                 if (!gplok) {
>                         printk(KERN_WARNING "Symbol %s is being used "
>                           "by a non-GPL module, which will not "
>                           "be allowed in the future\n", name);
>                         printk(KERN_WARNING "Please see the file "
>                           "Documentation/feature-removal-schedule.txt "
>                           "in the kernel source tree for more "
>                           "details.\n");
> ...
> 
>   but there's nothing in the feature removal file that expands on that
> issue.  (there *is* an entry regarding *unused* symbols, but that
> doesn't seem to address the above.)
EXPORT_GPL_FUTURE is used to mark _functionality_ as no longer available
after a grace period. So when one marks a set of symbols as GPL_FUTURE
that functionality ougt to be described in feature-removal.
Did you see any _functionaliy_ where GPL_FUTURE are used where it
is not warned in fetaure-removal that that _functionality_ are supposed
to be changed?

Or in other words - please be more specific.

	Sam

      reply	other threads:[~2007-06-09 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-09  9:25 Robert P. J. Day
2007-06-09 16:24 ` Sam Ravnborg [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=20070609162409.GB31493@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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®