From: David Howells <dhowells@redhat.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux390@de.ibm.com, linux-s390@vger.kernel.org, hch@lst.de,
apw@shadowen.org
Subject: Re: [PATCH] mm snapshot broken-out-2007-11-06-02-32 - conflict in vxfs_iget ()
Date: Tue, 06 Nov 2007 21:12:02 +0000 [thread overview]
Message-ID: <27341.1194383522@redhat.com> (raw)
In-Reply-To: <20071106200807.GC13674@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> The kernel build fails on S390, with error
I gave Andrew the attached patch which is very similar to yours.
David
[-- Attachment #2: 7861 --]
[-- Type: message/rfc822, Size: 2544 bytes --]
From: David Howells <dhowells@redhat.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, dhowells@redhat.com
Subject: [PATCH] IGET: Use ino_t consistently for vxfs_iget() and its declaration
Date: Tue, 06 Nov 2007 14:15:54 +0000
Message-ID: <20071106141554.17691.1661.stgit@warthog.procyon.org.uk>
Use ino_t consistently for vxfs_iget() and its declaration, rather than using
ino_t for one and unsigned long for the other.
Signed-off-by: David Howells <dhowells@redhat.com>
---
fs/freevxfs/vxfs_extern.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/freevxfs/vxfs_extern.h b/fs/freevxfs/vxfs_extern.h
index f307694..2b46064 100644
--- a/fs/freevxfs/vxfs_extern.h
+++ b/fs/freevxfs/vxfs_extern.h
@@ -58,7 +58,7 @@ extern struct inode * vxfs_get_fake_inode(struct super_block *,
extern void vxfs_put_fake_inode(struct inode *);
extern struct vxfs_inode_info * vxfs_blkiget(struct super_block *, u_long, ino_t);
extern struct vxfs_inode_info * vxfs_stiget(struct super_block *, ino_t);
-extern struct inode * vxfs_iget(struct super_block *, unsigned long);
+extern struct inode * vxfs_iget(struct super_block *, ino_t);
extern void vxfs_clear_inode(struct inode *);
/* vxfs_lookup.c */
prev parent reply other threads:[~2007-11-06 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 20:08 [PATCH] mm snapshot broken-out-2007-11-06-02-32 - conflict in vxfs_iget () Kamalesh Babulal
2007-11-06 21:12 ` 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=27341.1194383522@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=hch@lst.de \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=mm-commits@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 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.