From: Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>
To: Tom Fredrik Blenning Klaussen <bfg-kernel@blenning.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/config reducing kernel image size
Date: Tue, 14 Sep 2004 15:11:15 -0300 [thread overview]
Message-ID: <200409141511.15970.norberto+linux-kernel@bensa.ath.cx> (raw)
In-Reply-To: <1095184644.1838.11.camel@host-81-191-110-70.bluecom.no>
Tom Fredrik Blenning Klaussen wrote:
> On Tue, 2004-09-14 at 19:44, Norberto Bensa wrote:
> > Try this:
>
> You're right.
> Am I correct when I say that when an option is not present, it assumes
> it's default?
Exactly.
Best regards,
Norberto
prev parent reply other threads:[~2004-09-14 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 16:33 /proc/config reducing kernel image size Tom Fredrik Blenning Klaussen
2004-09-14 17:26 ` DervishD
2004-09-14 17:36 ` Tom Fredrik Blenning Klaussen
2004-09-14 18:01 ` DervishD
2004-09-15 10:11 ` Herbert Poetzl
2004-09-14 17:44 ` Norberto Bensa
2004-09-14 17:57 ` Tom Fredrik Blenning Klaussen
2004-09-14 18:11 ` Norberto Bensa [this message]
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=200409141511.15970.norberto+linux-kernel@bensa.ath.cx \
--to=norberto+linux-kernel@bensa.ath.cx \
--cc=bfg-kernel@blenning.no \
--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