From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: Chao Yu <chao2.yu@samsung.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
Changman Lee <cm224.lee@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: next-20151021 - compile error in fs/f2fs/checkpoint.c
Date: Wed, 21 Oct 2015 14:05:35 -0400 [thread overview]
Message-ID: <37662.1445450735@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
Building next-20151021 dies with this error:
CC [M] fs/f2fs/checkpoint.o
fs/f2fs/checkpoint.c: In function 'get_valid_checkpoint':
fs/f2fs/checkpoint.c:707:3: error: too few arguments to function 'ra_meta_pages'
ra_meta_pages(sbi, cp_blk_no + 1, cp_blks - 1, META_CP);
^
fs/f2fs/checkpoint.c:143:5: note: declared here
int ra_meta_pages(struct f2fs_sb_info *sbi, block_t start, int nrpages,
^
scripts/Makefile.build:258: recipe for target 'fs/f2fs/checkpoint.o' failed
make[2]: *** [fs/f2fs/checkpoint.o] Error 1
Looks like this commit:
commit 26879fb101f28c554294eaf25ac7817a2825b180
Author: Chao Yu <chao2.yu@samsung.com>
Date: Mon Oct 12 17:05:59 2015 +0800
f2fs: support lower priority asynchronous readahead in ra_meta_pages
missed updating one call. Apparently this wasn't compile-tested before
being pushed upstream?
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next reply other threads:[~2015-10-21 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 18:05 Valdis Kletnieks [this message]
2015-10-22 1:47 ` next-20151021 - compile error in fs/f2fs/checkpoint.c Chao Yu
2015-10-22 3:06 ` Jaegeuk Kim
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=37662.1445450735@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=chao2.yu@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).