From: kbuild test robot <fengguang.wu@intel.com>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
Cc: kbuild-all@01.org, Borislav Petkov <bp@suse.de>,
Doug Thompson <dougthompson@xmission.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [bp:for-next 15/22] drivers/edac/mce_amd_inj.c:47:21: sparse: symbol 'inj_type' was not declared. Should it be static?
Date: Fri, 5 Jun 2015 19:24:26 +0800 [thread overview]
Message-ID: <201506051907.ofv5fD3p%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp for-next
head: 6db4e6b99ba0dad4e42612a546a99ccdbd766561
commit: 0451d14d05618e5fcbdc5017a30e3d609ddc8229 [15/22] EDAC, mce_amd_inj: Modify flags attribute to use string arguments
reproduce:
# apt-get install sparse
git checkout 0451d14d05618e5fcbdc5017a30e3d609ddc8229
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/edac/mce_amd_inj.c:47:21: sparse: symbol 'inj_type' was not declared. Should it be static?
drivers/edac/mce_amd_inj.c:320:1: sparse: symbol '__UNIQUE_ID_author__COUNTER__' has multiple initializers (originally initialized at drivers/edac/mce_amd_inj.c:319)
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
next reply other threads:[~2015-06-05 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 11:24 kbuild test robot [this message]
2015-06-05 11:24 ` [PATCH bp] EDAC, mce_amd_inj: inj_type can be static kbuild test robot
2015-06-05 13:33 ` Borislav Petkov
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=201506051907.ofv5fD3p%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@suse.de \
--cc=dougthompson@xmission.com \
--cc=kbuild-all@01.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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