From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
adaplas@pol.net,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
dwmw2@redhat.com
Subject: Re: [PATCH] kill symbol_get & friends
Date: Thu, 13 Jan 2005 11:19:33 +1100 [thread overview]
Message-ID: <1105575573.12794.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20050112203136.GA3150@lst.de>
On Wed, 2005-01-12 at 21:31 +0100, Christoph Hellwig wrote:
> Rusty introduced symbol_get as a replacement for inter_module_get, but
> it doesn't really solved the underlying problem.
Sorry, Christoph, I must be particularly obtuse today.
If you don't hold a reference, then yes, the module can go away. This
hasn't been a huge problem for users in the past.
The lack of users is because, firstly, dynamic dependencies are less
common than static ones, and secondly because the remaining inter-module
users (AGP and mtd) have not been converted. Patches have been sent
several times, but maintainers are distracted, it seems. I *will* run
out of patience and push those patches which take away intermodule.c one
day (hint, hint!).
For optional module dependencies, weak symbols can be used, but there
seems to be a desire for genuine dynamic dependencies. If you can get
rid of those, I'll apply your patch in a second!
Cheers,
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-01-13 0:43 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 [this message]
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
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=1105575573.12794.27.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=dwmw2@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.