From: Keith Owens <kaos@ocs.com.au>
To: Al Peat <al_kernel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: put/get_module_symbol vs. inter_module_register/put/get/etc.
Date: Sat, 02 Dec 2000 10:09:47 +1100 [thread overview]
Message-ID: <21319.975712187@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 01 Dec 2000 10:52:35 -0800." <20001201185235.44106.qmail@web10105.mail.yahoo.com>
On Fri, 1 Dec 2000 10:52:35 -0800 (PST),
Al Peat <al_kernel@yahoo.com> wrote:
> I've followed the thread on "Persistent module
>storage" but haven't come across a general explanation
>of the changes to the inter-module symbol stuff
>between 2.4test10 and test11. Anyone care to comment
>on the differences or on whether this is going to be a
>stable API for 2.4 (it won't be changed again)?
You are confusing two completely different topics. inter_module_xxx
replaced get_module_symbol because the latter was a bad interface, it
violated module layering and broke when symbol versions were turned on.
inter_module_xxx is clean and stable, it has also been sent to Alan Cox
for inclusion in 2.2 kernels, although 2.2 will still have
get_module_symbol for backwards compatibility.
Persistent module data is the ability to save module parameters at
unload time. It only makes sense for parameters that are changed by
users after load, e.g. volume controls, TV tuner settings etc. That
facility is almost completely in user space and requires very few
changes to modules. Watch this space.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-01 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 18:52 put/get_module_symbol vs. inter_module_register/put/get/etc Al Peat
2000-12-01 23:09 ` 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=21319.975712187@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=al_kernel@yahoo.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