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@infradead.org
Subject: Re: [PATCH] kill symbol_get & friends
Date: Fri, 14 Jan 2005 17:56:50 +1100 [thread overview]
Message-ID: <1105685810.7311.96.camel@localhost.localdomain> (raw)
In-Reply-To: <20050113170528.GA24590@lst.de>
On Thu, 2005-01-13 at 18:05 +0100, Christoph Hellwig wrote:
> On Thu, Jan 13, 2005 at 11:19:33AM +1100, Rusty Russell wrote:
> > 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.
>
> There's a single users, and it has these problems.
It is an excellent candidate for weak symbols though. If you want the
symbols to stay around, of course you have to keep a reference to them.
This code seems silly to me.
> > 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.
>
> AGP doesn't use dynamic symbols anymore, only mtd is gone. And I'd
> rather see it not switching to symbol_get.
If it really wants dynamic symbol lookup, that's damn well what's going
to happen. intermodule must die. If David doesn't want that feature
any more, then sure, remove it.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-01-14 7:02 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 [this message]
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=1105685810.7311.96.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=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.