From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> To: Andrew Morton <akpm@linux-foundation.org> Cc: LKML <linux-kernel@vger.kernel.org>, linux-nilfs <linux-nilfs@vger.kernel.org>, Geliang Tang <geliangtang@gmail.com>, Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Subject: [PATCH -mm 0/2] nilfs2 minor changes Date: Tue, 24 Jan 2017 00:17:33 +0900 [thread overview] Message-ID: <1485184655-3895-1-git-send-email-konishi.ryusuke@lab.ntt.co.jp> (raw) Hi Andrew, Please queue the following changes for the next merge window: Geliang Tang (2): nilfs2: use nilfs_btree_node_size() nilfs2: use i_blocksize() where "nilfs2: use i_blocksize()" requires the patch "fs: add i_blocksize()" which resides in -mm tree. Meanwhile "nilfs2: use nilfs_btree_node_size()" is applicable independently. Thanks, Ryusuke Konishi -- fs/nilfs2/alloc.c | 2 +- fs/nilfs2/btree.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org> To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> Cc: LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Geliang Tang <geliangtang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org> Subject: [PATCH -mm 0/2] nilfs2 minor changes Date: Tue, 24 Jan 2017 00:17:33 +0900 [thread overview] Message-ID: <1485184655-3895-1-git-send-email-konishi.ryusuke@lab.ntt.co.jp> (raw) Hi Andrew, Please queue the following changes for the next merge window: Geliang Tang (2): nilfs2: use nilfs_btree_node_size() nilfs2: use i_blocksize() where "nilfs2: use i_blocksize()" requires the patch "fs: add i_blocksize()" which resides in -mm tree. Meanwhile "nilfs2: use nilfs_btree_node_size()" is applicable independently. Thanks, Ryusuke Konishi -- fs/nilfs2/alloc.c | 2 +- fs/nilfs2/btree.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-01-23 15:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-23 15:17 Ryusuke Konishi [this message] 2017-01-23 15:17 ` [PATCH -mm 0/2] nilfs2 minor changes Ryusuke Konishi 2017-01-23 15:17 ` [PATCH -mm 1/2] nilfs2: use nilfs_btree_node_size() Ryusuke Konishi 2017-01-23 15:17 ` [PATCH -mm 2/2] nilfs2: use i_blocksize() Ryusuke Konishi
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=1485184655-3895-1-git-send-email-konishi.ryusuke@lab.ntt.co.jp \ --to=konishi.ryusuke@lab.ntt.co.jp \ --cc=akpm@linux-foundation.org \ --cc=geliangtang@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nilfs@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: linkBe 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.