public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Keith Owens <kaos@ocs.com.au>,
	Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.17.2: make ext2 smaller
Date: Sun, 02 Dec 2001 08:03:27 -0500	[thread overview]
Message-ID: <3C0A269F.D2B1D3@mandrakesoft.com> (raw)
In-Reply-To: <3C0A1105.18B76D64@mandrakesoft.com> <25560.1007294074@ocs3.intra.ocs.com.au> <20011202133314.B717@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser wrote:
> On Sun, Dec 02, 2001 at 10:54:34PM +1100, Keith Owens wrote:
> > With kbuild 2.5 the generation of ext2_all.c (I prefer
> > ext2_static.c) can be automated.

> > The code that is normally linked into xxxx.o has to be manually changed
> > to add XXXX_STATIC before a make_static(xxxx) command can be added.

> Even this doesn't have to be done manually. Everything that is
> not covered by EXPORT_SYMBOL() in this case can be static, since

And if !MODULE, then even EXPORT_SYMBOL symbols can become static, if
they are not used outside the compilation unit.

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


  parent reply	other threads:[~2001-12-02 13:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02 11:31 PATCH 2.4.17.2: make ext2 smaller Jeff Garzik
2001-12-02 11:54 ` Keith Owens
2001-12-02 12:33   ` Ingo Oeser
2001-12-02 13:00     ` PATCH 2.4.17.2: CONFIG_FINAL, make kernel smaller Jeff Garzik
2001-12-02 13:07       ` Jeff Garzik
2001-12-02 13:03     ` Jeff Garzik [this message]
2001-12-02 13:40       ` PATCH 2.4.17.2: make ext2 smaller Ingo Oeser
2001-12-02 13:47         ` Jeff Garzik
2001-12-02 13:53           ` Ingo Oeser
2001-12-02 16:14 ` Christer Weinigel
2001-12-02 16:44 ` Martin Dalecki
2001-12-02 17:42   ` Jeff Garzik
2001-12-02 21:30 ` Andrew Morton
2001-12-02 21:35   ` Jeff Garzik
2001-12-03  2:53 ` Horst von Brand

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=3C0A269F.D2B1D3@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.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