From: David Howells <dhowells@redhat.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: Patch: romfs_lookup always failed in linux-2.6.25-rc3-git3
Date: Tue, 04 Mar 2008 22:25:56 +0000 [thread overview]
Message-ID: <9258.1204669556@redhat.com> (raw)
In-Reply-To: <20080304184009.GB24301@freya.fugue.com>
Adam J. Richter <adam@yggdrasil.com> wrote:
> My only question is why you've changed res from int to long, given that
> you've corrected my misguided "P.S.":
Because if you compile for a 64-bit system, you may find extra instructions
emitted, at the very least in ERR_PTR(res) where it turns a 32-bit int into a
64-bit pointer.
David
prev parent reply other threads:[~2008-03-04 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 17:36 Patch: romfs_lookup always failed in linux-2.6.25-rc3-git3 Adam J. Richter
2008-03-04 9:26 ` Andrew Morton
2008-03-04 18:19 ` Adam J. Richter
2008-03-04 14:32 ` David Howells
2008-03-04 18:40 ` Adam J. Richter
2008-03-04 22:25 ` David Howells [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=9258.1204669556@redhat.com \
--to=dhowells@redhat.com \
--cc=adam@yggdrasil.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).