[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110725123856.1e61415ac8e90d106d0585c8@canb.auug.org.au>
Date: Mon, 25 Jul 2011 12:38:56 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "Theodore Ts'o" <tytso@....edu>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@....de>,
Amir Goldstein <amir73il@...rs.sf.net>,
Al Viro <viro@...IV.linux.org.uk>
Subject: Re: linux-next: manual merge of the vfs tree with the ext4 tree
Hi all,
On Mon, 18 Jul 2011 13:36:25 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Today's linux-next merge of the vfs tree got a conflict in
> fs/ext4/inode.c between commit dae1e52cb126 ("ext4: move ext4_ind_*
> functions from inode.c to indirect.c") from the ext4 tree and commit
> d1769fea6879 ("fs: simplify the blockdev_direct_IO prototype") from the
> vfs tree.
>
> A function moved to a new file. I fixed it up and can carry the fix as
> necessary.
>
> I also needed the following merge fix patch:
This patchg is now needed after merging the ext4 tree with Linius' tree
(repeated here):
From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Mon, 18 Jul 2011 13:28:44 +1000
Subject: [PATCH] vfs/ext4: merge fixup for moved function
Signed-off-by: Stephen Rothwell <sfr@...b.auug.org.au>
---
fs/ext4/indirect.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/indirect.c b/fs/ext4/indirect.c
index 6c27111..b8602cd 100644
--- a/fs/ext4/indirect.c
+++ b/fs/ext4/indirect.c
@@ -806,10 +806,8 @@ retry:
offset, nr_segs,
ext4_get_block, NULL, NULL, 0);
else {
- ret = blockdev_direct_IO(rw, iocb, inode,
- inode->i_sb->s_bdev, iov,
- offset, nr_segs,
- ext4_get_block, NULL);
+ ret = blockdev_direct_IO(rw, iocb, inode, iov,
+ offset, nr_segs, ext4_get_block);
if (unlikely((rw & WRITE) && ret < 0)) {
loff_t isize = i_size_read(inode);
--
1.7.5.4
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists