From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Linus Torvalds <torvalds@osdl.org>,
"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Re: Linux 2.6.10-rc2
Date: Wed, 17 Nov 2004 23:37:04 +0000 [thread overview]
Message-ID: <200411172337.04192.andrew@walrond.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0411171504220.2222@ppc970.osdl.org>
On Wednesday 17 Nov 2004 23:12, Linus Torvalds wrote:
> On Wed, 17 Nov 2004, Andrew Walrond wrote:
> > And I can confirm that the problem exists in both 32bit and 64bit
> > kernels.
>
> Ok. None of the code should actually have changed at all, but I notice one
> bug:
>
>
> please undo those parts (by hand, I've messed up white-space), since they
> make "burst" be one too big. Looks like the reason for doing that in the
> first place was an old sparse warning that no longer exists.
>
Ok reverted and tested, but made no difference to corruption.
(I only tried 64bit kernel; I assume 32bit would behave similarly)
Andrew
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-17 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0411141835150.2222@ppc970.osdl.org>
2004-11-17 15:54 ` Linux 2.6.10-rc2 Andrew Walrond
[not found] ` <Pine.LNX.4.58.0411170802500.2222@ppc970.osdl.org>
2004-11-17 19:17 ` Andrew Walrond
2004-11-17 22:33 ` Andrew Walrond
2004-11-17 23:12 ` Linus Torvalds
2004-11-17 23:37 ` Andrew Walrond [this message]
2004-11-18 0:12 ` Antonino A. Daplas
2004-11-19 9:06 ` Guido Guenther
2004-11-18 0:01 ` Antonino A. Daplas
2004-11-18 10:19 ` Geert Uytterhoeven
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=200411172337.04192.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=torvalds@osdl.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).