mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sascha Andres" <linux-kernel@programmers-world.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Changed message for GPLONLY symbols
Date: Tue, 13 Nov 2001 19:22:28 +0100	[thread overview]
Message-ID: <001401c16c70$27297590$0328a8c0@keasanb> (raw)
In-Reply-To: <20011113113401.55b75a1b.reynolds@redhat.com>

hi,

i did not wrote much to this list yet, but i have a suggestion to this
hint:
> > 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.
>              ^^^^
^^^^^^^^^^^^^^^^^^^^^^^^

when i read the last sentence i had the feeling of a bad taste,
just because is sounds just like 'the evil module supplier (which
might just not have recompiled his modules yet) is responsible
for all and everything'.

well, it sounds like that for me.

what's with this:

To avoid further problems please contact the module supplier as he can
help you best.

so the whole hint would look like:

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).
	To avoid further problems please contact the module supplier as
he can
	help you best.

that is - i think - a bit more polite and perhaps it helps to prevent
mails like 'your damn module causes serious errors with the actual
kernel.
can't you program like you ought to program'. at least that mails
will be more polite too.

bye,

sascha



  parent reply	other threads:[~2001-11-13 18:21 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
2001-11-13 18:04   ` Alex Bligh - linux-kernel
2001-11-13 18:22   ` Sascha Andres [this message]
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='001401c16c70$27297590$0328a8c0@keasanb' \
    --to=linux-kernel@programmers-world.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®