From: Andi Kleen <ak@muc.de>
To: Yaroslav Klyukin <skintwin@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 and x86_64
Date: Tue, 23 Dec 2003 22:40:48 +0100 [thread overview]
Message-ID: <m3u13rcivz.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <162gF-8hY-27@gated-at.bofh.it> (Yaroslav Klyukin's message of "Tue, 23 Dec 2003 22:30:25 +0100")
Yaroslav Klyukin <skintwin@mail.ru> writes:
> Did anybody have any experience with %subj%?
> I am curious about stability.
There are several nasty bugs in 2.6.0/x86-64. Only
use it with the x86-64 patchkit (ftp://ftp.x86-64.org/pub/linux/v2.6/*)
-Andi
next parent reply other threads:[~2003-12-23 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <162gF-8hY-27@gated-at.bofh.it>
2003-12-23 21:40 ` Andi Kleen [this message]
2003-12-23 21:27 2.6.0 and x86_64 Yaroslav Klyukin
2003-12-23 21:50 ` Mike Fedyk
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=m3u13rcivz.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=skintwin@mail.ru \
/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.