public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: David Howells <dhowells@redhat.com>
Cc: 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, 4 Mar 2008 10:40:09 -0800	[thread overview]
Message-ID: <20080304184009.GB24301@freya.fugue.com> (raw)
In-Reply-To: <5368.1204641163@redhat.com>

On Tue, Mar 04, 2008 at 02:32:43PM +0000, David Howells wrote:
> [...] Can you look over the attached patch as an alternative, please?

	Your new goto labels "error" and "success" (instead of "out"
and "out0") clarify the code enough to justify your removal of the
comment block, so that's all good.  My only question is why you've
changed res from int to long, given that you've corrected my misguided
"P.S.":

> Adam J. Richter <adam@yggdrasil.com> wrote:
[...]
> > P.S. romfs_lookup casts a valid pointer to an int and then back again
> > with res = PTR_ERR(inode);...return ERR_PTR(res).  This may break on
> > arhictectures where sizeof(int) < sizeof(pointer).
> 
> This is not true.  [...]

	You're right.  My mistake.  Sorry for causing confusion.  But,
based on what you've just said, it doesn't sound like you need to
change res from int to long.  Is there some other issue I'm missing?

	Anyhow, if you want to do these changes together in a single
commit or separately, I'm fine with it either way.

Adam Richter

  reply	other threads:[~2008-03-04 18:40 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 [this message]
2008-03-04 22:25     ` David Howells

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=20080304184009.GB24301@freya.fugue.com \
    --to=adam@yggdrasil.com \
    --cc=dhowells@redhat.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