From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [driver-core:driver-core-next 4/11] include/linux/device.h:925:12: error: 'dev_vprintk_emit' defined
Date: Tue, 02 Oct 2012 10:41:27 +0000 [thread overview]
Message-ID: <20121002104127.GA31577@localhost> (raw)
Hi Joe,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git driver-core-next
head: e0f21e6d52cc245e7d4f7e02ca4b7b6571660ec2
commit: 05e4e5b87aab74f994acf9dd4bed4a8f1367cd09 [4/11] dev: Add dev_vprintk_emit and dev_printk_emit
config: sh-allnoconfig
All error/warnings:
include/linux/device.h:925:12: error: 'dev_vprintk_emit' defined but not used [-Werror=unused-function]
cc1: all warnings being treated as errors
vim +925 include/linux/device.h
b9075fa9 (Joe Perches 2011-10-31 919) int dev_notice(const struct device *dev, const char *fmt, ...);
b9075fa9 (Joe Perches 2011-10-31 920) extern __printf(2, 3)
b9075fa9 (Joe Perches 2011-10-31 921) int _dev_info(const struct device *dev, const char *fmt, ...);
99bcf217 (Joe Perches 2010-06-27 922)
99bcf217 (Joe Perches 2010-06-27 923) #else
99bcf217 (Joe Perches 2010-06-27 924)
05e4e5b8 (Joe Perches 2012-09-12 @925) static int dev_vprintk_emit(int level, const struct device *dev,
05e4e5b8 (Joe Perches 2012-09-12 926) const char *fmt, va_list args)
05e4e5b8 (Joe Perches 2012-09-12 927) { return 0; }
05e4e5b8 (Joe Perches 2012-09-12 928) static inline __printf(3, 4)
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
next reply other threads:[~2012-10-02 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 10:41 Fengguang Wu [this message]
2012-10-02 13:46 ` [driver-core:driver-core-next 4/11] include/linux/device.h:925:12: error: 'dev_vprintk_emit' def Greg Kroah-Hartman
2012-10-02 13:54 ` Joe Perches
2012-10-02 14:06 ` Fengguang Wu
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=20121002104127.GA31577@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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