From: brian@worldcontrol.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CIPE vs. GPLONLY_
Date: Fri, 11 Jan 2002 20:57:31 -0800 [thread overview]
Message-ID: <20020112045731.GA3788@top.worldcontrol.com> (raw)
In-Reply-To: <20020112010317.GA1765@top.worldcontrol.com> <E16PD12-0000wY-00@the-village.bc.nu>
In-Reply-To: <E16PD12-0000wY-00@the-village.bc.nu>
On Sat, Jan 12, 2002 at 01:31:24AM +0000, Alan Cox wrote:
> > running CIPE 1.5.2 I get the error above. Should I be bother the
> > CIPE people with this? Or is this some kernel thingy that needs
> > to be dealt with?
>
> Add
>
> MODULE_LICENSE("GPL");
>
> to the cipe code and all will be well
As I posted in another email. The above changed helped but I still
had one undef'ed reference.
I removed my linux source tree, rebuilt everything, and now it
works fine.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
next prev parent reply other threads:[~2002-01-12 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 1:03 CIPE vs. GPLONLY_ brian
2002-01-12 1:31 ` Alan Cox
2002-01-12 1:48 ` brian
2002-01-12 3:26 ` Arnaldo Carvalho de Melo
2002-01-12 4:57 ` brian [this message]
2002-01-12 11:37 ` Olaf Titz
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=20020112045731.GA3788@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.