From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: is bzImage container large enough?
Date: Sat, 1 Sep 2001 13:42:29 -0700 [thread overview]
Message-ID: <20010901134229.A16630@thune.mrc-home.com> (raw)
In-Reply-To: <22500.999376181@ocs3.ocs-net>
On Sun, Sep 02, 2001 at 06:29:41AM +1000, Keith Owens wrote:
> allmod and make randconfig. Included in separate mail.
randconfig?
This scares me. :->
Btw, are such things independent of CML being used? Was wondering if a
"randconfig" might use CML2 to validate the configuration (as far as CML2
knows about it). _Might_ be useful to enhance CML2 to track down
incompatible configurations.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2001-09-01 20:42 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
2001-09-01 20:41 ` Tom Gall
2001-09-01 23:49 ` Anton Blanchard
2001-09-01 20:42 ` Mike Castle [this message]
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=20010901134229.A16630@thune.mrc-home.com \
--to=dalgoda@ix.netcom.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