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 3/3] NTB: Add flush_req and wakeup interface
Date: Thu, 17 Dec 2015 19:29:59 +0800 [thread overview]
Message-ID: <201512171934.tXqXjAPO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1450340292-18994-1-git-send-email-Xiangliang.Yu@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2982 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: In function 'amd_ntb_mw_set_trans':
drivers/ntb/hw/amd/ntb_hw_amd.c:189:6: warning: 'limit' may be used uninitialized in this function [-Wmaybe-uninitialized]
if (reg_val != limit) {
^
drivers/ntb/hw/amd/ntb_hw_amd.c: In function 'amd_ntb_wakeup_peer_side':
>> drivers/ntb/hw/amd/ntb_hw_amd.c:526:6: warning: 'reg' may be used uninitialized in this function [-Wmaybe-uninitialized]
reg |= 0x1;
^
drivers/ntb/hw/amd/ntb_hw_amd.c:518:6: note: 'reg' was declared here
u32 reg;
^
vim +/reg +526 drivers/ntb/hw/amd/ntb_hw_amd.c
58a6d117 Xiangliang Yu 2015-12-17 510 return amd_flush_peer_requests(ndev);
58a6d117 Xiangliang Yu 2015-12-17 511 }
58a6d117 Xiangliang Yu 2015-12-17 512
a635755a Xiangliang Yu 2015-12-17 513 /*
a635755a Xiangliang Yu 2015-12-17 514 * wake up the peer side
a635755a Xiangliang Yu 2015-12-17 515 */
a635755a Xiangliang Yu 2015-12-17 516 static int amd_wakeup_peer_side(struct amd_ntb_dev *ndev)
a635755a Xiangliang Yu 2015-12-17 517 {
a635755a Xiangliang Yu 2015-12-17 518 u32 reg;
a635755a Xiangliang Yu 2015-12-17 519
a635755a Xiangliang Yu 2015-12-17 520 if (!amd_link_is_up(ndev)) {
a635755a Xiangliang Yu 2015-12-17 521 dev_warn(ndev_dev(ndev), "link is down.\n");
a635755a Xiangliang Yu 2015-12-17 522 return -EINVAL;
a635755a Xiangliang Yu 2015-12-17 523 }
a635755a Xiangliang Yu 2015-12-17 524
a635755a Xiangliang Yu 2015-12-17 525 NTB_READ_REG(PMSGTRIG);
a635755a Xiangliang Yu 2015-12-17 @526 reg |= 0x1;
a635755a Xiangliang Yu 2015-12-17 527 NTB_WRITE_REG(reg, PMSGTRIG);
a635755a Xiangliang Yu 2015-12-17 528
a635755a Xiangliang Yu 2015-12-17 529 wait_for_completion(&ndev->wakeup_cmpl);
a635755a Xiangliang Yu 2015-12-17 530
a635755a Xiangliang Yu 2015-12-17 531 return 0;
a635755a Xiangliang Yu 2015-12-17 532 }
a635755a Xiangliang Yu 2015-12-17 533
58a6d117 Xiangliang Yu 2015-12-17 534 static int amd_ntb_wakeup_peer_side(struct ntb_dev *ntb)
:::::: The code at line 526 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:30 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:29 ` 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=201512171934.tXqXjAPO%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®