mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Walter <trwalter@apex.net>
To: Richard Russon <kernel@flatcap.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug database braindump from the kernel summit
Date: Mon, 2 Apr 2001 16:35:10 -0500	[thread overview]
Message-ID: <20010402163510.A26109@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1010401181724.28121i-100000@mandrakesoft.mandrakesoft.com> <986189206.789.0.camel@home.flatcap.org>
In-Reply-To: <986189206.789.0.camel@home.flatcap.org>; from kernel@flatcap.org on Mon, Apr 02, 2001 at 06:26:45AM +0100

On Mon, Apr 02, 2001 at 06:26:45AM +0100, Richard Russon wrote:
> On 01 Apr 2001 18:21:29 -0500, Jeff Garzik wrote:
> > Let's hope it's not a flamewar, but here goes :)
> > 
> > We -need- .config, but /proc/config seems like pure bloat.
> 
> Don't ask me for sample code, but...
> 
> The init code for many drivers is freed up after it's used.
> Could we apply the same technique and compile in .config,
> then printk the entire lot (boot option) and free up the
> space afterwards?

Though this would save memory at run-time, you'd still increase the size
of the image.

-- 
-Steven
Freedom is the freedom to say that two plus two equals four.

  reply	other threads:[~2001-04-02 21:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01 19:32 Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07   ` Jeff Garzik
2001-04-01 21:48     ` Manfred Spraul
2001-04-01 22:48       ` Jeff Garzik
2001-04-01 23:01         ` David Lang
2001-04-01 23:21           ` Jeff Garzik
2001-04-01 23:25             ` David Lang
2001-04-01 23:34               ` Jeff Garzik
2001-04-01 23:32                 ` David Lang
2001-04-01 23:44                   ` Jeff Garzik
2001-04-01 23:43                     ` David Lang
2001-04-02  0:26                       ` Ben Ford
2001-04-05 12:55                         ` Petr Baudis
2001-04-02 18:57                       ` Kai Henningsen
2001-04-02  5:26             ` Richard Russon
2001-04-02 21:35               ` Steven Walter [this message]
2001-04-02 19:39             ` Oliver Xymoron
2001-04-02 21:40               ` J . A . Magallon
2001-04-02 22:09                 ` Jeff Garzik
2001-04-02 22:24                   ` David Lang
2001-04-02 22:38                   ` J . A . Magallon
2001-04-02 23:04               ` Tom Leete
2001-04-02 23:12                 ` Oliver Xymoron
2001-04-02 23:24                   ` Jeff Garzik
2001-04-02 23:31                     ` Oliver Xymoron
2001-04-03 16:05                   ` Miles Lane
2001-04-02  1:49     ` Miles Lane
2001-04-01 20:59 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-04-01 22:34 Stephen Satchell
2001-04-02  8:00 ` Olaf Titz
2001-04-01 17:54 Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21   ` Gregory Maxwell
2001-04-01 20:38     ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18   ` David Lang
2001-04-02  1:57   ` Miles Lane
2001-04-02  5:07     ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff

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=20010402163510.A26109@hapablap.dyn.dhs.org \
    --to=trwalter@apex.net \
    --cc=kernel@flatcap.org \
    --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

all inboxes | Powered by JetHome®