From: David Woodhouse <dwmw2@infradead.org>
To: "Song Sam" <samlinuxppc@yahoo.com.cn>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 versus 2.6 patches
Date: Mon, 26 Jul 2004 00:13:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0407260009310.4160@localhost.localdomain> (raw)
In-Reply-To: <20040726025057.68338.qmail@web15204.mail.bjs.yahoo.com>
On Mon, 26 Jul 2004, [gb2312] Song Sam wrote:
> But 2.4 kernel is still a pet for 8xx,at least.I guess
> many embedded Linux development lean to 2.4 kernel for
> the moment.For Linux kernel hackers,2.4 kernel was
> dead but it is alive for most embedded
> developers.Right? :-)
I cannot speak for 'most embedded developers.'; only those with clue.
I would not consider deploying anything new on 2.4 today; it's just
not a viable, maintainable platform in my opinion.
--
dwmw2
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-26 4:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 14:57 2.4 versus 2.6 patches Robert P. J. Day
2004-07-24 15:20 ` David Woodhouse
2004-07-26 2:50 ` Song Sam
2004-07-26 4:13 ` David Woodhouse [this message]
2004-07-26 4:40 ` Eugene Surovegin
2004-07-26 13:48 ` Song Sam
2004-07-26 14:27 ` David Woodhouse
2004-07-26 15:08 ` Mark Chambers
2004-07-26 15:53 ` Robert P. J. Day
2004-07-26 16:30 ` Eugene Surovegin
2004-07-26 23:17 ` Thomas Gleixner
2004-07-26 23:49 ` Eugene Surovegin
2004-07-27 0:25 ` Thomas Gleixner
2004-07-29 19:30 ` David Woodhouse
2004-07-26 17:16 ` Wolfgang Denk
2004-08-09 15:03 ` Marcelo Tosatti
2004-07-27 3:13 ` Song Sam
2004-08-09 13:28 ` Marcelo Tosatti
2004-08-10 5:58 ` Song Sam
2004-08-10 11:54 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 16:48 Demke, Torsten
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.4.58.0407260009310.4160@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
--cc=samlinuxppc@yahoo.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).