From: Dmitry Golubev <dmitry@mikrotik.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] embedding 2.6 or more findings on kernel size
Date: Wed, 1 Sep 2004 02:41:20 +0300 [thread overview]
Message-ID: <200409010241.20950.dmitry@mikrotik.com> (raw)
In-Reply-To: <20040831202707.GQ3466@fs.tum.de>
> Please don't include this.
what a good start...
> I'd prefer to switch i386 cpu selection to a different scheme which
> gives you effectively these options for free without additional options.
I admit, I might have missed the latest version of your patch, but in what I
have seen, some functionality have been missing comparing to my patch
(do you have a possibility to compile a kernel especially for NexGen,
Transmeta or UMC?), and it also changes user experience, which obviously
should not happen in the stable branch. However, it might be a good idea to
work on your patch for v 2.7.
Anyway, if you would like, I can separate CPU support part of the patch from
the other parts...
Dmitry
prev parent reply other threads:[~2004-09-01 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 20:07 embedding 2.6 or more findings on kernel size Dmitry Golubev
2004-08-31 14:10 ` [PATCH] " Dmitry Golubev
2004-08-31 20:27 ` Adrian Bunk
2004-08-31 23:41 ` Dmitry Golubev [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=200409010241.20950.dmitry@mikrotik.com \
--to=dmitry@mikrotik.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--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