From: kbuild test robot <lkp@intel.com>
To: Xiangliang Yu <Xiangliang.Yu@amd.com>
Cc: kbuild-all@01.org, jdmason@kudzu.us, dave.jiang@intel.com,
Allen.Hubbe@emc.com, linux-ntb@googlegroups.com,
linux-kernel@vger.kernel.org, SPG_Linux_Kernel@amd.com,
Xiangliang Yu <Xiangliang.Yu@amd.com>
Subject: Re: [PATCH 2/3] NTB: Add AMD NTB support in Kconfig and Makefile
Date: Thu, 17 Dec 2015 19:01:56 +0800 [thread overview]
Message-ID: <201512171806.MNDZUp6G%fengguang.wu@intel.com> (raw)
In-Reply-To: <1450340280-18953-1-git-send-email-Xiangliang.Yu@amd.com>
[-- Attachment #1: Type: text/plain, Size: 3303 bytes --]
Hi Xiangliang,
[auto build test WARNING on v4.4-rc5]
[also build test WARNING on next-20151217]
url: https://github.com/0day-ci/linux/commits/Xiangliang-Yu/NTB-Add-AMD-PCI-Express-NTB-driver/20151217-113608
config: x86_64-randconfig-n0-12171710 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/ntb/hw/amd/ntb_hw_amd.c:486:12: warning: 'amd_flush_peer_requests' defined but not used [-Wunused-function]
static int amd_flush_peer_requests(struct amd_ntb_dev *ndev)
^
drivers/ntb/hw/amd/ntb_hw_amd.c:507:12: warning: 'amd_wakeup_peer_side' defined but not used [-Wunused-function]
static int amd_wakeup_peer_side(struct amd_ntb_dev *ndev)
^
drivers/ntb/hw/amd/ntb_hw_amd.c: In function 'amd_ntb_mw_set_trans':
>> drivers/ntb/hw/amd/ntb_hw_amd.c:187:6: warning: 'limit' may be used uninitialized in this function [-Wmaybe-uninitialized]
if (reg_val != limit) {
^
vim +/limit +187 drivers/ntb/hw/amd/ntb_hw_amd.c
a635755a Xiangliang Yu 2015-12-17 171 if (bar != 1) {
a635755a Xiangliang Yu 2015-12-17 172 /* Set the limit if supported */
a635755a Xiangliang Yu 2015-12-17 173 if (limit_reg)
a635755a Xiangliang Yu 2015-12-17 174 limit = base_addr + size;
a635755a Xiangliang Yu 2015-12-17 175
a635755a Xiangliang Yu 2015-12-17 176 /* set and verify setting the translation address */
a635755a Xiangliang Yu 2015-12-17 177 iowrite64(addr, peer_mmio + xlat_reg);
a635755a Xiangliang Yu 2015-12-17 178 reg_val = ioread64(peer_mmio + xlat_reg);
a635755a Xiangliang Yu 2015-12-17 179 if (reg_val != addr) {
a635755a Xiangliang Yu 2015-12-17 180 iowrite64(0, peer_mmio + xlat_reg);
a635755a Xiangliang Yu 2015-12-17 181 return -EIO;
a635755a Xiangliang Yu 2015-12-17 182 }
a635755a Xiangliang Yu 2015-12-17 183
a635755a Xiangliang Yu 2015-12-17 184 /* set and verify setting the limit */
a635755a Xiangliang Yu 2015-12-17 185 iowrite64(limit, mmio + limit_reg);
a635755a Xiangliang Yu 2015-12-17 186 reg_val = ioread64(mmio + limit_reg);
a635755a Xiangliang Yu 2015-12-17 @187 if (reg_val != limit) {
a635755a Xiangliang Yu 2015-12-17 188 iowrite64(base_addr, mmio + limit_reg);
a635755a Xiangliang Yu 2015-12-17 189 iowrite64(0, peer_mmio + xlat_reg);
a635755a Xiangliang Yu 2015-12-17 190 return -EIO;
a635755a Xiangliang Yu 2015-12-17 191 }
a635755a Xiangliang Yu 2015-12-17 192 } else {
a635755a Xiangliang Yu 2015-12-17 193 /* split bar addr range must all be 32 bit */
a635755a Xiangliang Yu 2015-12-17 194 if (addr & (~0ull << 32))
a635755a Xiangliang Yu 2015-12-17 195 return -EINVAL;
:::::: The code at line 187 was first introduced by commit
:::::: a635755a710138a6f505cc7e62693741786fb19e NTB: Add AMD PCI-Express NTB driver
:::::: TO: Xiangliang Yu <Xiangliang.Yu@amd.com>
:::::: CC: 0day robot <fengguang.wu@intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28696 bytes --]
prev parent reply other threads:[~2015-12-17 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 8:18 Xiangliang Yu
2015-12-17 11:01 ` kbuild test robot [this message]
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=201512171806.MNDZUp6G%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Allen.Hubbe@emc.com \
--cc=SPG_Linux_Kernel@amd.com \
--cc=Xiangliang.Yu@amd.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.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
all inboxes | Powered by JetHome®