From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: eis@baty.hanse.de, netdev@oss.sgi.com
Subject: Re: [PATCH] Remove MOD_* from LAPB
Date: Sat, 19 Jul 2003 21:44:58 -0700 [thread overview]
Message-ID: <20030719214458.2ea87a94.davem@redhat.com> (raw)
In-Reply-To: <20030718133211.1c7ed08d.shemminger@osdl.org>
On Fri, 18 Jul 2003 13:32:11 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> The MOD_INC and MOD_DEC in lapb are no longer necessary in 2.6 since
> the module subsystem will not allow lapb to be unloaded as long as a module
> that is referencing the symbols (lapb_register/lapb_unregister) is loaded.
>
> The lapb parameter block does have callback's so it is up to the caller
> to correctly unregister on module exit; and looking at the existing code
> it does do that.
Applied, thanks.
prev parent reply other threads:[~2003-07-20 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 20:32 [PATCH] Remove MOD_* from LAPB Stephen Hemminger
2003-07-18 22:01 ` [PATCH] Allow lapb to be unloaded Stephen Hemminger
2003-07-20 4:47 ` David S. Miller
2003-07-20 4:44 ` David S. Miller [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=20030719214458.2ea87a94.davem@redhat.com \
--to=davem@redhat.com \
--cc=eis@baty.hanse.de \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).