All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@jaquet.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] CONFIG_TINY
Date: Thu, 24 Oct 2002 22:38:47 +0200	[thread overview]
Message-ID: <20021024223847.C18085@jaquet.dk> (raw)
In-Reply-To: <20021023215117.A29134@jaquet.dk>; from rasmus@jaquet.dk on Wed, Oct 23, 2002 at 09:51:17PM +0200

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

On Wed, Oct 23, 2002 at 09:51:17PM +0200, Rasmus Andersen wrote:
> printk: So far I have defined {i,d,n,w}prink corresponding to
> KERN_ {INFO,DEBUG,NOTICE,WARNING} and have converted files to
> use this. Higher levels are left untouched.
> 
[...]
> 
>    text    data     bss     dec     hex filename
>  478109   50337  254560  783006   bf29e vmlinux   (woo! :)
> 
> (Patch at www.jaquet.dk/kernel/config_tiny/2.5.43-printk)

Memo to me: Dont use the kernel compiled to check #define
correctness for enabling printk output to measure the kernel
size when prinkt is disabled. New, better kernel size:

   text    data     bss     dec     hex filename
 475629   50913  252512  779054   be32e vmlinux


Regards, 
  Rasmus

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2002-10-24 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 19:51 [RFC] CONFIG_TINY Rasmus Andersen
2002-10-23 17:11 ` Joe Perches
2002-10-24 20:40   ` Rasmus Andersen
2002-10-23 20:08 ` Christoph Hellwig
2002-10-23 20:39   ` Rasmus Andersen
2002-10-24  3:01 ` Elladan
2002-10-25  5:19   ` Untested patch 1/2 - add ugly printk macros to kernel (was Re: [RFC] CONFIG_TINY) Elladan
2002-10-25  5:20   ` Untested patch 2/2 - Fix some kernel sources for macro printk " Elladan
2002-10-24 20:38 ` Rasmus Andersen [this message]
2002-10-25 21:45 ` [RFC] CONFIG_TINY Daniel Phillips

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=20021024223847.C18085@jaquet.dk \
    --to=rasmus@jaquet.dk \
    --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 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.