From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.3-rc3-mm1
Date: Mon, 16 Feb 2004 14:19:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1040216141554.2146A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040216095411.1592d09d.akpm@osdl.org>
On Mon, 16 Feb 2004, Andrew Morton wrote:
> Bill Davidsen <davidsen@tmr.com> wrote:
> >
> > > - Dropped the x86 CPU-type selection patches
> >
> > Was there a problem with this? Seems like a good start to allow cleaning
> > up some "but I don't have that CPU" things which embedded and tiny
> > systems really would like to eliminate.
>
> I think it was a good change, and was appropriate to 2.5.x. But for 2.6.x
> the benefit didn't seem to justify the depth of the change.
And will it be appropriate for 2.7? It really does give a start to
trimming code you don't want in a small kernel, and would have been nice
so people could use it for any processor specific additions to 2.6.
Not arguing, but it was a step to improve control of creeping unnecessary
archetecture support.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-16 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 9:58 2.6.3-rc3-mm1 Andrew Morton
2004-02-16 11:39 ` 2.6.3-rc3-mm1 Krishnakumar. R
2004-02-16 12:16 ` 2.6.3-rc3-mm1 Bill Davidsen
2004-02-16 17:54 ` 2.6.3-rc3-mm1 Andrew Morton
2004-02-16 19:19 ` Bill Davidsen [this message]
2004-02-16 21:12 ` 2.6.3-rc3-mm1 Zwane Mwaikambo
2004-02-16 21:29 ` 2.6.3-rc3-mm1 Andrew Morton
2004-02-17 21:26 ` 2.6.3-rc3-mm1 Zwane Mwaikambo
2004-02-16 19:23 ` 2.6.3-rc3-mm1 (compile stats) John Cherry
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=Pine.LNX.3.96.1040216141554.2146A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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