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:N0 23/30] fs/fs_context.c:382:3: error: implicit declaration of function 'vprintk_emit'
Date: Tue, 13 Nov 2018 10:37:41 +0800 [thread overview]
Message-ID: <201811131039.AVM7umM6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git N0
head: a595a8b3e7dbb7d47eb7303baf5ad2fae39664a1
commit: 121e8d139044e8d5de23ec76c2b2c10d27a1df68 [23/30] vfs: Implement logging through fs_context
config: openrisc-allnoconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 6.0.0 20160327 (experimental)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 121e8d139044e8d5de23ec76c2b2c10d27a1df68
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All errors (new ones prefixed by >>):
fs/fs_context.c: In function 'logfc':
>> fs/fs_context.c:382:3: error: implicit declaration of function 'vprintk_emit' [-Werror=implicit-function-declaration]
vprintk_emit(0, LOGLEVEL_WARNING, NULL, 0, fmt, va);
^~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/vprintk_emit +382 fs/fs_context.c
368
369 /**
370 * logfc - Log a message to a filesystem context
371 * @fc: The filesystem context to log to.
372 * @fmt: The format of the buffer.
373 */
374 void logfc(struct fs_context *fc, const char *fmt, ...)
375 {
376 va_list va;
377
378 va_start(va, fmt);
379
380 switch (fmt[0]) {
381 case 'w':
> 382 vprintk_emit(0, LOGLEVEL_WARNING, NULL, 0, fmt, va);
383 break;
384 case 'e':
385 vprintk_emit(0, LOGLEVEL_ERR, NULL, 0, fmt, va);
386 break;
387 default:
388 vprintk_emit(0, LOGLEVEL_NOTICE, NULL, 0, fmt, va);
389 break;
390 }
391
392 pr_cont("\n");
393 va_end(va);
394 }
395 EXPORT_SYMBOL(logfc);
396
---
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: 4424 bytes --]
reply other threads:[~2018-11-13 13:04 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=201811131039.AVM7umM6%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).