From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org, announce@x86-64.org
Cc: linux-kernel@vger.kernel.org
Subject: x86-64 2.4 tree in strict maintenance mode now
Date: Wed, 14 Apr 2004 17:43:53 +0200 [thread overview]
Message-ID: <20040414174353.1dcbda16.ak@suse.de> (raw)
2.4.26 has been finally released. It includes the patches for Intel support and
a few other bug fixes for x86-64. This was about the latest feature I planned
to merge (in fact one more than originally planned)
2.4/x86-64 is currently in a quite good shape. It is widely used and seems to
generally work well. 2.6 is also good enough now to be used in production.
As far as I'm concerned the 2.4 port of x86-64 is in strict maintenance mode now.
This means no features will not be accepted anymore; only very clear bug fixes that
fix serious bugs (like oopses or security holes)
In particular this means that the 32bit emulation is frozen now; any missing ioctls
etc. are not bugs and will not be fixed in mainline.
I will also not add workarounds for broken hardware to 2.4 anymore unless the change
is very simple and obvious (and even then it may be not worth it)
For example the recent VIA IOMMU breakage workaround is already 2.6
only with no plans to backport. If you have buggy or very new hardware you may need
to migrate to 2.6.
This also means that the 2.4 CVS kernel tree on x86-64.org will be retired.
I expect that the small obvious bug fixes that should be still merged will
be all sent directly to Marcelo and put into the main tree; so there is no need
for an x86-64 private tree anymore.
If you want to do any features or cleanups for x86-64 work on 2.6.
-Andi
next reply other threads:[~2004-04-14 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 15:43 Andi Kleen [this message]
2004-04-16 15:00 ` [discuss] x86-64 2.4 tree in strict maintenance mode now Pavel Machek
2004-04-16 15:46 ` Andi Kleen
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=20040414174353.1dcbda16.ak@suse.de \
--to=ak@suse.de \
--cc=announce@x86-64.org \
--cc=discuss@x86-64.org \
--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