From: kbuild test robot <lkp@intel.com>
To: Thomas Rowland <trowland2000@gmail.com>
Cc: kbuild-all@01.org, aar@pengutronix.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Rowland <trowland2000@gmail.com>
Subject: Re: [PATCH] include: net: cfg802154: rename ieee802154_llsec_device.hwaddr to extended_addr
Date: Tue, 21 Jun 2016 18:49:26 +0800 [thread overview]
Message-ID: <201606211827.sT7sqMKB%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466504548-2958-1-git-send-email-trowland2000@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]
Hi,
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Thomas-Rowland/include-net-cfg802154-rename-ieee802154_llsec_device-hwaddr-to-extended_addr/20160621-182617
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
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
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
net/mac802154/llsec.c: In function 'llsec_dev_find_long':
>> net/mac802154/llsec.c:333:15: error: 'struct ieee802154_llsec_device' has no member named 'hwaddr'
if (dev->dev.hwaddr == hwaddr)
^
net/mac802154/llsec.c: In function 'llsec_lookup_dev':
net/mac802154/llsec.c:799:16: error: 'struct ieee802154_llsec_device' has no member named 'hwaddr'
if (dev->dev.hwaddr == devaddr.extended_addr)
^
net/mac802154/llsec.c: In function 'mac802154_llsec_decrypt':
net/mac802154/llsec.c:1037:21: error: 'struct ieee802154_llsec_device' has no member named 'hwaddr'
dev_addr = dev->dev.hwaddr;
^
vim +333 net/mac802154/llsec.c
5d637d5a Phoebe Buckheister 2014-05-16 327 llsec_dev_find_long(struct mac802154_llsec *sec, __le64 hwaddr)
5d637d5a Phoebe Buckheister 2014-05-16 328 {
5d637d5a Phoebe Buckheister 2014-05-16 329 struct mac802154_llsec_device *dev;
5d637d5a Phoebe Buckheister 2014-05-16 330 u64 key = llsec_dev_hash_long(hwaddr);
5d637d5a Phoebe Buckheister 2014-05-16 331
5d637d5a Phoebe Buckheister 2014-05-16 332 hash_for_each_possible_rcu(sec->devices_hw, dev, bucket_hw, key) {
5d637d5a Phoebe Buckheister 2014-05-16 @333 if (dev->dev.hwaddr == hwaddr)
5d637d5a Phoebe Buckheister 2014-05-16 334 return dev;
5d637d5a Phoebe Buckheister 2014-05-16 335 }
5d637d5a Phoebe Buckheister 2014-05-16 336
:::::: The code at line 333 was first introduced by commit
:::::: 5d637d5aabd85132bd85779677d8acb708e0ed90 mac802154: add llsec structures and mutators
:::::: TO: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
:::::: CC: David S. Miller <davem@davemloft.net>
---
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: 46453 bytes --]
next prev parent reply other threads:[~2016-06-21 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:22 Thomas Rowland
2016-06-21 10:49 ` kbuild test robot [this message]
2016-06-21 11:27 ` kbuild test robot
2016-06-21 11:29 ` kbuild test robot
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=201606211827.sT7sqMKB%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aar@pengutronix.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trowland2000@gmail.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®