From: Rusty Russell <rusty@rustcorp.com.au>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lib.a causing modules not to load
Date: Mon, 17 Nov 2003 13:47:34 +1100 [thread overview]
Message-ID: <20031117060542.088D32C0B1@lists.samba.org> (raw)
In-Reply-To: Your message of "08 Nov 2003 09:16:10 MDT." <1068304571.2048.5.camel@mulgrave>
In message <1068304571.2048.5.camel@mulgrave> you write:
> On Sat, 2003-11-08 at 02:51, Christoph Hellwig wrote:
> > On Fri, Nov 07, 2003 at 08:34:19PM -0800, Andrew Morton wrote:
> > > How about we just link that function into the kernel and be done with it?
> > > We'll waste a few bytes on SMP machines which have neither ext2 nor ext3
> > > linked-in or loaded as modules, but that doesn't sound very important...
> > >
> > > (We don't have a kernel/random-support-stuff.c, but we have
> > > mm/random-support-stuff.c which for some reason is called mm/swap.c, so
> > > I put it there).
> >
> > Well, this solves the problem for this particular case, but not other
> > stuff in lib for other situations.
>
> I agree...there's much more in lib than just percpu_counter_mod.
I think lib.a should be linked as is if !CONFIG_MODULES, and done as a
..o if CONFIG_MODULES. Other alternatives are possible, but make it
tricky if someone adds a module later which wants something in lib.a.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-11-17 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 16:21 James Bottomley
2003-11-07 16:27 ` James Bottomley
2003-11-08 4:34 ` Andrew Morton
2003-11-08 8:51 ` Christoph Hellwig
2003-11-08 15:16 ` James Bottomley
2003-11-17 2:47 ` Rusty Russell [this message]
2003-11-18 16:25 ` James Bottomley
2003-11-19 0:06 ` 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=20031117060542.088D32C0B1@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.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
Powered by JetHome