From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [vfs:Q33 23/62] fs/fs_context.c:370:3: error: implicit declaration of function 'vprintk_emit'; did you mean 'dev_printk_emit'?
Date: Fri, 21 Dec 2018 08:37:25 +0800 [thread overview]
Message-ID: <201812210803.Ykdw2HuE%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git Q33
head: 7137da19ff622a80c07afb57e5a79794f0d7d54d
commit: 78434c707f30f5464fd1a1b7a7fa1692ded1d30a [23/62] vfs: Implement logging through fs_context
config: riscv-tinyconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 78434c707f30f5464fd1a1b7a7fa1692ded1d30a
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=riscv
Note: the vfs/Q33 HEAD 7137da19ff622a80c07afb57e5a79794f0d7d54d builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
fs/fs_context.c: In function 'logfc':
>> fs/fs_context.c:370:3: error: implicit declaration of function 'vprintk_emit'; did you mean 'dev_printk_emit'? [-Werror=implicit-function-declaration]
vprintk_emit(0, LOGLEVEL_WARNING, NULL, 0, fmt, va);
^~~~~~~~~~~~
dev_printk_emit
cc1: some warnings being treated as errors
vim +370 fs/fs_context.c
356
357 /**
358 * logfc - Log a message to a filesystem context
359 * @fc: The filesystem context to log to.
360 * @fmt: The format of the buffer.
361 */
362 void logfc(struct fs_context *fc, const char *fmt, ...)
363 {
364 va_list va;
365
366 va_start(va, fmt);
367
368 switch (fmt[0]) {
369 case 'w':
> 370 vprintk_emit(0, LOGLEVEL_WARNING, NULL, 0, fmt, va);
371 break;
372 case 'e':
373 vprintk_emit(0, LOGLEVEL_ERR, NULL, 0, fmt, va);
374 break;
375 default:
376 vprintk_emit(0, LOGLEVEL_NOTICE, NULL, 0, fmt, va);
377 break;
378 }
379
380 pr_cont("\n");
381 va_end(va);
382 }
383 EXPORT_SYMBOL(logfc);
384
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 4428 bytes --]
reply other threads:[~2018-12-21 0:37 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=201812210803.Ykdw2HuE%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).