The patch titled
Subject: nilfs2: use nilfs_btree_node_size()
has been added to the -mm tree. Its filename is
nilfs2-use-nilfs_btree_node_size.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/nilfs2-use-nilfs_btree_node_size.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/nilfs2-use-nilfs_btree_node_size.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Geliang Tang <geliangtang@xxxxxxxxx>
Subject: nilfs2: use nilfs_btree_node_size()
Use nilfs_btree_node_size() instead of open-coding.
Link: http://lkml.kernel.org/r/1485184655-3895-2-git-send-email-konishi.ryusuke@xxxxxxxxxxxxx
Signed-off-by: Geliang Tang <geliangtang@xxxxxxxxx>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/nilfs2/btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/nilfs2/btree.c~nilfs2-use-nilfs_btree_node_size fs/nilfs2/btree.c
--- a/fs/nilfs2/btree.c~nilfs2-use-nilfs_btree_node_size
+++ a/fs/nilfs2/btree.c
@@ -1870,7 +1870,7 @@ int nilfs_btree_convert_and_insert(struc
di = &dreq;
ni = NULL;
} else if ((n + 1) <= NILFS_BTREE_NODE_NCHILDREN_MAX(
- 1 << btree->b_inode->i_blkbits)) {
+ nilfs_btree_node_size(btree))) {
di = &dreq;
ni = &nreq;
} else {
_
Patches currently in -mm which might be from geliangtang@xxxxxxxxx are
mm-vmallocc-use-rb_entry_safe.patch
writeback-use-rb_entry.patch
proc-use-rb_entry.patch
nilfs2-use-nilfs_btree_node_size.patch
nilfs2-use-i_blocksize.patch
fs-add-i_blocksize-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
