From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.4
Date: Thu, 11 Mar 2004 08:49:43 +0100 [thread overview]
Message-ID: <200403110849.43527.lkml@kcore.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403101924510.3693@ppc970.osdl.org>
On Thursday 11 March 2004 04:28, Linus Torvalds wrote:
> A few small fixes since -rc3, most notably an OHCI bug that would corrupt
> memory and seems to have been the reason for the "Bad page flags" bug at
> least on ppc64 (it's not been reported on x86, as far as I know, but I
> don't see why the corruption couldn't have happened there too).
>
> The full changelog from 2.6.3 is on the ftp-sites along with the patches
> and tar-balls, and the BK trees have been updated.
>
> Linus
Just upgraded from 2.6.2 to 2.6.4. The new -mregparm=3 support, how likely is
it to totally break one's system? I'm not really in the mood to trash boxes
today ;p
Jan
--
Innocence ends when one is stripped of the delusion that one likes oneself.
-- Joan Didion, "On Self Respect"
next prev parent reply other threads:[~2004-03-11 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 3:28 Linux 2.6.4 Linus Torvalds
2004-03-11 7:49 ` Jan De Luyck [this message]
2004-03-11 16:58 ` Pavel Machek
2004-03-12 18:13 ` Linux 2.6.4 (compile stats) John Cherry
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=200403110849.43527.lkml@kcore.org \
--to=lkml@kcore.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