From: kbuild test robot <lkp@intel.com>
To: miaoqing@codeaurora.org
Cc: kbuild-all@01.org, linville@tuxdriver.com,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
kvalo@qca.qualcomm.com, Miaoqing Pan <miaoqing@codeaurora.org>
Subject: Re: [PATCH] ath9k: feeding entropy in kernel from ADC capture
Date: Wed, 30 Sep 2015 05:30:30 +0800 [thread overview]
Message-ID: <201509300525.Dq22K55n%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443493680-8189-1-git-send-email-miaoqing@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]
Hi Miaoqing,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: tile-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 220286596260e48c3c25675309d3c7d4f0875198
# save the attached .config to linux build tree
make.cross ARCH=tile
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/net/wireless/ath/ath9k/rng.c: In function 'ath9k_rng_data_read.constprop.0':
>> drivers/net/wireless/ath/ath9k/rng.c:53:15: warning: 'v2' may be used uninitialized in this function [-Wuninitialized]
vim +/v2 +53 drivers/net/wireless/ath/ath9k/rng.c
37 REG_RMW_FIELD(ah, AR_PHY_TEST_CTL_STATUS, AR_PHY_TEST_CTL_RX_OBS_SEL, 0);
38
39 for (i = 0, j = 0; i < buf_size; i++) {
40 v1 = REG_READ(ah, AR_PHY_TST_ADC) & 0xffff;
41 v2 = REG_READ(ah, AR_PHY_TST_ADC) & 0xffff;
42
43 /* wait for data ready */
44 if (v1 && v2 && rng_last != v1 && v1 != v2 && v1 != 0xffff &&
45 v2 != 0xffff)
46 buf[j++] = (v1 << 16) | v2;
47
48 rng_last = v2;
49 }
50
51 ath9k_ps_restore(sc);
52
> 53 sc->rng_last = v2;
54
55 return j << 2;
56 }
57
58 static int ath9k_rng_kthread(void *data)
59 {
60 int bytes_read;
61 struct ath_softc *sc = data;
---
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: 41626 bytes --]
next prev parent reply other threads:[~2015-09-29 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 2:28 [PATCH] ath9k: feeding entropy in kernel from ADC capture miaoqing
2015-09-29 21:30 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-30 3:07 miaoqing
2015-09-30 3:12 ` Pan, Miaoqing
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=201509300525.Dq22K55n%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=kbuild-all@01.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=miaoqing@codeaurora.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