From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [mips:upstream 10/22] arch/mips/kernel/proc.c:75:3: warning: too many arguments for format
Date: Mon, 15 Oct 2012 02:20:26 +0000 [thread overview]
Message-ID: <20121015022026.GD7203@localhost> (raw)
In-Reply-To: <20121015015300.GE31881@yliu-dev.sh.intel.com>
Hi Steven,
FYI, there are new compile warnings show up in
tree: git://git.linux-mips.org/pub/scm/ralf/upstream-linus.git upstream
head: 35bafbee4b4732a2820bbd0ef141c8192ff29731
commit: ee80f7c73dc1b1f0ba9f82079c9bd1c0d1aedef8 [10/22] MIPS: Add detection of DSP ASE Revision 2.
config: mips-allyesconfig # make ARCH=mips
All warnings:
arch/mips/kernel/proc.c: In function 'show_cpuinfo':
arch/mips/kernel/proc.c:75:3: warning: too many arguments for format [-Wformat-extra-args]
vim +75 arch/mips/kernel/proc.c
e027802e Ralf Baechle 2005-08-16 67 seq_printf(m, "ASEs implemented\t:%s%s%s%s%s%s\n",
4194318c Ralf Baechle 2005-05-05 68 cpu_has_mips16 ? " mips16" : "",
4194318c Ralf Baechle 2005-05-05 69 cpu_has_mdmx ? " mdmx" : "",
4194318c Ralf Baechle 2005-05-05 70 cpu_has_mips3d ? " mips3d" : "",
e027802e Ralf Baechle 2005-08-16 71 cpu_has_smartmips ? " smartmips" : "",
e027802e Ralf Baechle 2005-08-16 72 cpu_has_dsp ? " dsp" : "",
ee80f7c7 Steven J. Hill 2012-08-03 73 cpu_has_dsp2 ? " dsp2" : "",
e027802e Ralf Baechle 2005-08-16 74 cpu_has_mipsmt ? " mt" : ""
e027802e Ralf Baechle 2005-08-16 @75 );
The code at line 75 was first introduced by commit:
e027802 Display presence of SmartMIPS, DSP and MT ASEs in /proc/cpuinfo.
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
next prev parent reply other threads:[~2012-10-15 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 1:53 [mips:upstream 10/22] arch/mips/kernel/proc.c:75:3: warning: too many arguments for format Yuanhan Liu
2012-10-15 2:20 ` Fengguang Wu [this message]
2012-10-15 8:56 ` Ralf Baechle
2012-10-15 9:17 ` Yuanhan Liu
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=20121015022026.GD7203@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