All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Smith, Todd" <Todd.Smith@camc.org>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: MIPS Kernel size
Date: Tue, 3 Feb 2004 16:16:25 +0100	[thread overview]
Message-ID: <20040203151625.GB27848@linux-mips.org> (raw)
In-Reply-To: <490E0430C3C72046ACF7F18B7CD76A2A56955E@KES.camcare.com>

On Mon, Feb 02, 2004 at 04:48:43PM -0500, Smith, Todd wrote:

> I like the idea of the -tiny tree and I hope that these changes get merged
> back into the main kernel tree.  One of Linux's historic advantages is that
> it can run on older equipment but the trend seems to be supporting only
> current equipment

Remember Linux development is user driven.  If you think it doesn't run
well enough on your small system then it's time to heat up your
C compiler :-)

  Ralf

  parent reply	other threads:[~2004-02-03 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 21:48 MIPS Kernel size Smith, Todd
2004-02-03 13:41 ` Maciej W. Rozycki
2004-02-03 15:17   ` Ralf Baechle
2004-02-03 14:50 ` Jan-Benedict Glaw
2004-02-03 15:18   ` Ralf Baechle
2004-02-03 16:52     ` Jan-Benedict Glaw
2004-02-03 17:07       ` Ralf Baechle
2004-02-03 15:16 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02 16:12 Smith, Todd
2004-02-02 18:53 ` Ralf Baechle
2004-01-27 14:51 kip.r2
2004-01-27 16:10 ` Thiemo Seufer
2004-02-02 14:09 ` Ralf Baechle
2004-02-02 18:43   ` Karsten Merker
2004-02-02 18:57     ` Ralf Baechle
2004-02-02 19:38       ` Geert Uytterhoeven
2004-02-02 19:46         ` Ralf Baechle
2004-02-02 19:50           ` Geert Uytterhoeven
2004-02-02 19:59             ` Ralf Baechle
2004-02-02 20:07               ` Thiemo Seufer
2004-02-02 20:32                 ` Ralf Baechle
2004-02-02 22:29         ` Peter Horton

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=20040203151625.GB27848@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Todd.Smith@camc.org \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.