From: akpm@linux-foundation.org
To: kamalesh@linux.vnet.ibm.com, mm-commits@vger.kernel.org
Subject: - iget-stop-bfs-from-using-iget-and-read_inode-try-fix.patch removed from -mm tree
Date: Wed, 06 Feb 2008 19:33:34 -0800 [thread overview]
Message-ID: <200802070333.m173XF2C014032@imap1.linux-foundation.org> (raw)
The patch titled
Build Fail - fs/bfs/inode.c
has been removed from the -mm tree. Its filename was
iget-stop-bfs-from-using-iget-and-read_inode-try-fix.patch
This patch was dropped because it was folded into iget-stop-bfs-from-using-iget-and-read_inode-try.patch
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: Build Fail - fs/bfs/inode.c
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
fs/bfs/inode.c: In function `bfs_iget':
fs/bfs/inode.c:37: error: `ino' redeclared as different kind of symbol
fs/bfs/inode.c:35: error: previous definition of `ino' was here
fs/bfs/inode.c:37: error: `inode' undeclared (first use in this function)
fs/bfs/inode.c:37: error: (Each undeclared identifier is reported onlyonce
fs/bfs/inode.c:37: error: for each function it appears in.)
Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/bfs/inode.c | 1 -
1 file changed, 1 deletion(-)
diff -puN fs/bfs/inode.c~iget-stop-bfs-from-using-iget-and-read_inode-try-fix fs/bfs/inode.c
--- a/fs/bfs/inode.c~iget-stop-bfs-from-using-iget-and-read_inode-try-fix
+++ a/fs/bfs/inode.c
@@ -34,7 +34,6 @@ void dump_imap(const char *prefix, struc
struct inode *bfs_iget(struct super_block *sb, unsigned long ino)
{
- unsigned long ino = inode->i_ino;
struct bfs_inode *di;
struct inode *inode;
struct buffer_head *bh;
_
Patches currently in -mm which might be from kamalesh@linux.vnet.ibm.com are
origin.patch
iget-stop-bfs-from-using-iget-and-read_inode-try.patch
iget-stop-bfs-from-using-iget-and-read_inode-try-fix.patch
reply other threads:[~2008-02-07 3:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200802070333.m173XF2C014032@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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.