From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [vfs:for-jlayton 16/28] fs/hpfs/inode.c:285:3: error: implicit declaration of function 'hpfs_truncate'
Date: Thu, 20 Dec 2012 23:18:43 +0000 [thread overview]
Message-ID: <20121220231843.GL4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <50d39b27.mnyVhgNq20ez3KSg%fengguang.wu@intel.com>
On Fri, Dec 21, 2012 at 07:11:35AM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-jlayton
> head: a1e960b5b25f19886a17d9f362bb0b06fcdf73f5
> commit: 93502ce5a271c577b2d2401ad873beeed3af4e6e [16/28] hpfs: drop vmtruncate
> config: make ARCH=x86_64 allmodconfig
>
> All error/warnings:
>
> fs/hpfs/inode.c: In function 'hpfs_setattr':
> fs/hpfs/inode.c:285:3: error: implicit declaration of function 'hpfs_truncate' [-Werror=implicit-function-declaration]
Grr... OK, that needs making that sucker non-static, for starters
prev parent reply other threads:[~2012-12-20 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 23:11 [vfs:for-jlayton 16/28] fs/hpfs/inode.c:285:3: error: implicit declaration of function 'hpfs_truncate' kbuild test robot
2012-12-20 23:18 ` Al Viro [this message]
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=20121220231843.GL4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marco.stornelli@gmail.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;
as well as URLs for NNTP newsgroup(s).