public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.17.2: make ext2 smaller
Date: Sun, 02 Dec 2001 22:54:34 +1100	[thread overview]
Message-ID: <25560.1007294074@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 02 Dec 2001 06:31:17 CDT." <3C0A1105.18B76D64@mandrakesoft.com>

On Sun, 02 Dec 2001 06:31:17 -0500, 
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>Simply, all ext2 files are #include'd into a single file, ext2_all.c,
>and all functions and data structures are declared static.

I like it.  With kbuild 2.5 the generation of ext2_all.c (I prefer
ext2_static.c) can be automated.

objlink(ext2.o balloc.o bitmap.o dir.o file.o fsync.o ialloc.o inode.o ioctl.o
        namei.o super.o symlink.o)
select(CONFIG_EXT2_FS ext2.o)
make_static(ext2)

make_static(xxxx), which does not exist yet -

* Checks if CONFIG_MAKE_STATIC is set.
* Takes the objlink information from the kbuild 2.5 database.
* Automatically creates xxxx_static.c as a series of #include
  statements for the source files derived from objlink.
* Replaces the objlink data with objlink(xxxx.o xxxx_static.o).
* Compiles xxxx_static.c with -DXXXX_STATIC=static.

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.


  reply	other threads:[~2001-12-02 11:55 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 [this message]
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     ` PATCH 2.4.17.2: make ext2 smaller Jeff Garzik
2001-12-02 13:40       ` 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=25560.1007294074@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=jgarzik@mandrakesoft.com \
    --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