From: akpm@linux-foundation.org
To: geliangtang@gmail.com, ross.zwisler@linux.intel.com,
mm-commits@vger.kernel.org
Subject: + fs-add-i_blocksize-fix.patch added to -mm tree
Date: Fri, 20 Jan 2017 14:53:26 -0800 [thread overview]
Message-ID: <588294e6.ZfLS2+gdn8VMVmAz%akpm@linux-foundation.org> (raw)
The patch titled
Subject: truncate: use i_blocksize()
has been added to the -mm tree. Its filename is
fs-add-i_blocksize-fix.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/fs-add-i_blocksize-fix.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/fs-add-i_blocksize-fix.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@gmail.com>
Subject: truncate: use i_blocksize()
Since i_blocksize() helper has been defined in fs.h, use it instead
of open-coding.
Link: http://lkml.kernel.org/r/9c8b2cd83c8f5653805d43debde9fa8817e02fc4.1484895804.git.geliangtang@gmail.com
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/truncate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/truncate.c~fs-add-i_blocksize-fix mm/truncate.c
--- a/mm/truncate.c~fs-add-i_blocksize-fix
+++ a/mm/truncate.c
@@ -785,7 +785,7 @@ EXPORT_SYMBOL(truncate_setsize);
*/
void pagecache_isize_extended(struct inode *inode, loff_t from, loff_t to)
{
- int bsize = 1 << inode->i_blkbits;
+ int bsize = i_blocksize(inode);
loff_t rounded_from;
struct page *page;
pgoff_t index;
_
Patches currently in -mm which might be from geliangtang@gmail.com are
mm-vmallocc-use-rb_entry_safe.patch
writeback-use-rb_entry.patch
proc-use-rb_entry.patch
timerqueue-use-rb_entry_safe.patch
fs-add-i_blocksize-fix.patch
reply other threads:[~2017-01-20 22:53 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=588294e6.ZfLS2+gdn8VMVmAz%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=geliangtang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox