From: Keith Owens <kaos@ocs.com.au>
To: Willy TARREAU <willy@w.ods.org>
Cc: David Dyck <david.dyck@fluke.com>, Adrian Bunk <bunk@stusta.de>,
marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: upgrading modutils may have fixed: unresolved symbols still in 2.4.30-rc2 (usbserial needs symbol tty_ldisc_ref and tty_ldisc_deref which are EXPORT_SYMBOL_GPL)
Date: Tue, 29 Mar 2005 00:53:19 +1000 [thread overview]
Message-ID: <10606.1112021599@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 28 Mar 2005 13:37:31 +0200." <20050328113731.GA2131@pcw.home.local>
On Mon, 28 Mar 2005 13:37:31 +0200,
Willy TARREAU <willy@w.ods.org> wrote:
>On Mon, Mar 28, 2005 at 09:00:59PM +1000, Keith Owens wrote:
>> You need modutils >= 2.4.14 to use the combination of
>> CONFIG_MODVERSIONS with EXPORT_SYMBOL_GPL() on 2.4 kernels.
>
>Thanks for the precision Keith.
>
>So the following seems appropriate ?
>
>--- ./Documentation/Changes.old Sat Mar 26 07:42:46 2005
>+++ ./Documentation/Changes Mon Mar 28 13:35:06 2005
>@@ -52,7 +52,7 @@
> o Gnu make 3.77 # make --version
> o binutils 2.9.1.0.25 # ld -v
> o util-linux 2.10o # fdformat --version
>-o modutils 2.4.10 # insmod -V
>+o modutils 2.4.14 # insmod -V
> o e2fsprogs 1.25 # tune2fs
> o jfsutils 1.0.12 # fsck.jfs -V
> o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs
>
Ack.
prev parent reply other threads:[~2005-03-28 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 18:52 unresolved symbols still in 2.4.30-rc2 (usbserial needs symbol tty_ldisc_ref and tty_ldisc_deref which are EXPORT_SYMBOL_GPL) David Dyck
2005-03-26 19:13 ` Adrian Bunk
2005-03-26 20:39 ` David Dyck
2005-03-27 0:31 ` upgrading modutils may have fixed: " David Dyck
2005-03-27 8:33 ` Jan Engelhardt
2005-03-28 4:20 ` Willy Tarreau
2005-03-28 11:00 ` Keith Owens
2005-03-28 11:37 ` Willy TARREAU
2005-03-28 14:53 ` Keith Owens [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=10606.1112021599@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=bunk@stusta.de \
--cc=david.dyck@fluke.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=willy@w.ods.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.