From: Francois Romieu <romieu@fr.zoreil.com>
To: Ihar Philips Filipau <filia@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_EMBEDDED in vanilla
Date: Sun, 27 Jul 2003 17:08:18 +0200 [thread overview]
Message-ID: <20030727170818.A26615@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <3F23E2CA.7070107@softhome.net>; from filia@softhome.net on Sun, Jul 27, 2003 at 04:33:46PM +0200
Ihar Philips Filipau <filia@softhome.net> :
[...]
> And those patches were not mine.
Testing/submitting/improving/syncing needs some generous amount of
time. You can easily help the author (especially) when things don't
evolve.
[...]
> [ I was playing only with network code - and I was concerned with
> performance more, than with image size. And had no luck achiving
> something. ]
Try harder :o)
[...]
> I have grepped thru 2.6.0-test0 - but I can find only entries in
> defconfigs - but no mentions in .h/.c files.
KConfig ?
[...]
> And yes - this option doesn't work in 'make menuconfig'.
No kernel tree at hand to figure what "doesn't work" mean but:
ed .config<<EOD
/# CONFIG_EMBEDDED is not set
d
wq
EOD
make oldconfig
works like a charm here.
If something seems wrong with 'make menuconfig', feel free to submit
a detailled PR here or through bugzilla.kernel.org (as long as it
isn't a networking thing).
[...]
> and more than 500 additional CONFIG_* parameters comparing to vanilla.
Provided the vendor can afford an army of kernel hackers to maintain
it, it is fine.
No need to Cc: me, I am subscribed to l-k.
--
Ueimor
prev parent reply other threads:[~2003-07-27 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dcQ9.7aj.35@gated-at.bofh.it>
[not found] ` <dcQ9.7aj.31@gated-at.bofh.it>
[not found] ` <dhFS.3R3.11@gated-at.bofh.it>
[not found] ` <dSm7.4TZ.5@gated-at.bofh.it>
[not found] ` <dTrN.5Te.7@gated-at.bofh.it>
2003-07-27 14:33 ` OT: Vanilla not for embedded?! Re: Kernel 2.6 size increase - get_current()? Ihar "Philips" Filipau
2003-07-27 15:08 ` Francois Romieu [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=20030727170818.A26615@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=filia@softhome.net \
--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®