From: Rusty Russell <rusty@rustcorp.com.au>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
adaplas@pol.net,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
dwmw2@infradead.org
Subject: Re: [PATCH] kill symbol_get & friends
Date: Mon, 17 Jan 2005 13:47:21 +1100 [thread overview]
Message-ID: <1105930041.3954.7.camel@localhost.localdomain> (raw)
In-Reply-To: <037701c4fc0c$87abd910$0f01a8c0@max>
On Sun, 2005-01-16 at 20:46 +0000, Richard Purdie wrote:
> Without symbol_get, you can only have hard dependencies between the modules
> and hence you would be forced into loading both modules even if you only
> want one of them.
>
> I came across this function when trying to solve this exact problem. If the
> function is going to be removed, what is the alternative? Apologies if I've
> missed something obvious...
The workaround is to put some registration wedge in the core code (see
net/core/netfilter.c:808 for an example).
But this is exactly what symbol_get is for. However, if noone needs it,
we can remove it, as keeping infrastructure around because "someone
might need it" is not usually a good idea.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2005-01-17 2:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 20:31 [PATCH] kill symbol_get & friends Christoph Hellwig
2005-01-13 0:19 ` Rusty Russell
2005-01-13 0:59 ` Dave Airlie
2005-01-13 2:25 ` Rusty Russell
2005-01-13 8:42 ` David Woodhouse
2005-01-13 4:18 ` Dave Jones
2005-01-13 8:45 ` David Woodhouse
2005-01-13 17:05 ` Christoph Hellwig
2005-01-14 6:56 ` Rusty Russell
2005-01-16 20:46 ` Richard Purdie
2005-01-17 2:47 ` Rusty Russell [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=1105930041.3954.7.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=torvalds@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