From: Brian Uhrain <buhrain@rosettastone.com>
To: Alexander Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: can anybody check that the attached patch eliminates reiser4 compilation warnings on 64bit platforms?
Date: Thu, 06 Apr 2006 08:51:26 +0100 [thread overview]
Message-ID: <4434C87E.1040308@rosettastone.com> (raw)
In-Reply-To: <200604061120.37578.zam@namesys.com>
Hello,
Alexander Zarochentsev wrote:
> would you please help to check the attached patch (for 2.6.17-rc1-mm1)
> because our Alpha does not want to boot now.
I'm not sure what the last kernel version you had booting was (or what
the error is now the your Alpha system does not want to boot), but I
recently discovered a problem with kernels booting on my Alpha that was
introduced in one of the 2.6.16-rc's. Yesterday I was able to track
down and squash the bug, and submitted my patch (two versions, one for
2.6.16.1 and the other for 2.6.17-rc1) to the LKML. After fixing the
issue with CPU initialization, which looks like it would affect any
Alpha system as it was a case of things changing/being added in all of
the other architectures but not for the Alpha architecture, the system
has been running fine with a 2.6.16.1 kernel and reiser4 root
filesystem. :) You can find my email with the patch at
http://lkml.org/lkml/mbox/2006/4/5/69
- Brian
BTW, your patch to silence the printf-style format string argument
warnings looks fine to me. :)
prev parent reply other threads:[~2006-04-06 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 7:20 can anybody check that the attached patch eliminates reiser4 compilation warnings on 64bit platforms? Alexander Zarochentsev
2006-04-06 7:51 ` Brian Uhrain [this message]
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=4434C87E.1040308@rosettastone.com \
--to=buhrain@rosettastone.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.com \
/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.