From: Bernd Eckenfels <ecki-lkm@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 -> 2.2 differences?
Date: Sat, 26 Jul 2003 01:29:55 +0200 [thread overview]
Message-ID: <E19gC0Z-0001RR-00@calista.inka.de> (raw)
In-Reply-To: <20030725142434.GS32585@rdlg.net>
In article <20030725142434.GS32585@rdlg.net> you wrote:
> With all the SCO fun going on I have people asking me what functionality
> we would loose if we rolled from 2.4.21 kernel to the last known stable
> 2.2 kernel.
it is easier to turn off SMP.
BTW: what will happen if there is some SMP code from IBM in the kernel which
is owned by SCO? Isnt it a matter of days to remove that code? Does anybody
have to pay for past usage of the code?
Bernd
--
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
next prev parent reply other threads:[~2003-07-25 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 14:24 2.4 -> 2.2 differences? Robert L. Harris
2003-07-25 18:08 ` Mike Fedyk
2003-07-25 22:34 ` jw schultz
2003-07-25 23:29 ` Bernd Eckenfels [this message]
2003-07-26 0:02 ` Alan Cox
2003-07-26 0:47 ` Robert L. Harris
2003-07-26 12:36 ` Alan Cox
2003-07-26 22:49 ` Robert L. Harris
2003-07-26 15:25 ` Geert Uytterhoeven
2003-07-28 15:00 ` Robert L. Harris
2003-07-31 19:32 ` Andrew Scott
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=E19gC0Z-0001RR-00@calista.inka.de \
--to=ecki-lkm@lina.inka.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;
as well as URLs for NNTP newsgroup(s).