public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is bzImage container large enough?
Date: Sun, 02 Sep 2001 06:29:41 +1000	[thread overview]
Message-ID: <22500.999376181@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 01 Sep 2001 16:28:06 GMT." <200109011628.f81GS6R01079@vegae.deep.net>

On Sat, 1 Sep 2001 16:28:06 +0000 (UTC), 
Samium Gromoff <_deepfire@mail.ru> wrote:
>      If one wanting to turn on virtually every kernel CONFIG_* option
>  in order to check if the kernel compiles and then report possible
>  gcc errors to lkml, will the resulting kernel fit the bzImage format?

No, it is far too big.

BTW, if you want to test compiles against various combinations of
config, there are kbuild patches that add make allyes, make allno, make
allmod and make randconfig.  Included in separate mail.


  reply	other threads:[~2001-09-01 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01 16:28 is bzImage container large enough? Samium Gromoff
2001-09-01 20:29 ` Keith Owens [this message]
2001-09-01 20:41   ` Tom Gall
2001-09-01 23:49     ` Anton Blanchard
2001-09-01 20:42   ` Mike Castle
2001-09-01 20:49     ` Keith Owens

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=22500.999376181@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=_deepfire@mail.ru \
    --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