mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tommy Reynolds <reynolds@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Changed message for GPLONLY symbols
Date: Tue, 13 Nov 2001 11:34:01 -0600	[thread overview]
Message-ID: <20011113113401.55b75a1b.reynolds@redhat.com> (raw)
In-Reply-To: <2349543194.1005671437@[10.132.113.67]>
In-Reply-To: <10444.1005619809@kao2.melbourne.sgi.com> <2349543194.1005671437@[10.132.113.67]>

[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]

It was a dark and stormy night.  Suddenly "Alex Bligh - linux-kernel" <linux-kernel@alex.org.uk> began to type:

> Keith,
> 
> --On Tuesday, November 13, 2001 1:50 PM +1100 Keith Owens <kaos@ocs.com.au> 
> wrote:
> 
> > Hint: You are trying to load a module without a GPL compatible license
> >       and it has unresolved symbols.  The module may be trying to access
> >       GPLONLY symbols but the problem is more likely to be a coding or
> >       user error.  Contact the module supplier for assistance.
> >
> > Does anyone think that this message can be misunderstood by anybody
> > with the "intelligence" of the normal Windoze user?
> 
> Yes I think it can be misunderstood, and, perhaps more importantly, still
> points the user at GPLONLY when it's more likely to be a straightforward
> version mismatch. Better might be:
> 
> Hint: You are trying to load a module which has unresolved symbols. These
>       symbols may not be exported by this version of the kernel (perhaps
>       you have a version mismatch), or they may be exported GPLONLY,
>       (in which case they will not be available to your module which does
>       not carry a GPL compatible license). In either case, contact
>       the *only* module supplier for assistance; no one else can help you.
             ^^^^                                  ^^^^^^^^^^^^^^^^^^^^^^^^

---------------------------------------------+-----------------------------
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2001-11-13 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13  2:50 Keith Owens
2001-11-13  3:01 ` Richard Gooch
2001-11-13  3:20   ` Keith Owens
2001-11-13 20:54     ` Riley Williams
2001-11-13  6:12 ` andrew may
2001-11-13  6:39 ` Anthony DeRobertis
2001-11-14  1:40   ` Mike Fedyk
2001-11-28 23:02     ` Dr. Kelsey Hudson
2001-11-13 11:19 ` Skip Ford
2001-11-13 17:10 ` Alex Bligh - linux-kernel
2001-11-13 17:34 ` Tommy Reynolds [this message]
2001-11-13 18:04   ` Alex Bligh - linux-kernel
2001-11-13 18:22   ` Sascha Andres
2001-11-13 20:50 ` Riley Williams
2001-11-15 18:11 ` Brian Beattie
2001-11-27  2:20 Michael T. Babcock

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=20011113113401.55b75a1b.reynolds@redhat.com \
    --to=reynolds@redhat.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®