Linux IA64 platform development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] nfc: don't be making arch specific unaligned decisions at driver level.
Date: Mon, 09 Jan 2017 00:47:33 +0000	[thread overview]
Message-ID: <201701090805.NVKb2IVs%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170109001907.101949-1-paul.gortmaker@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2798 bytes --]

Hi Paul,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc3 next-20170106]
[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/Paul-Gortmaker/nfc-don-t-be-making-arch-specific-unaligned-decisions-at-driver-level/20170109-082915
config: x86_64-randconfig-x008-201702 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/nfc/nfcmrvl/fw_dnld.c: In function 'process_state_fw_dnld':
>> drivers/nfc/nfcmrvl/fw_dnld.c:287:9: error: implicit declaration of function 'get_unaligned_le16' [-Werror=implicit-function-declaration]
      len = get_unaligned_le16(&len);
            ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors
--
   drivers/nfc/nxp-nci/firmware.c: In function 'nxp_nci_fw_send_chunk':
>> drivers/nfc/nxp-nci/firmware.c:124:2: error: implicit declaration of function 'put_unaligned_be16' [-Werror=implicit-function-declaration]
     put_unaligned_be16(header, skb_put(skb, NXP_NCI_FW_HDR_LEN));
     ^~~~~~~~~~~~~~~~~~
   drivers/nfc/nxp-nci/firmware.c: In function 'nxp_nci_fw_send':
>> drivers/nfc/nxp-nci/firmware.c:151:25: error: implicit declaration of function 'get_unaligned_be16' [-Werror=implicit-function-declaration]
      fw_info->frame_size = get_unaligned_be16(fw_info->data) &
                            ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/get_unaligned_le16 +287 drivers/nfc/nfcmrvl/fw_dnld.c

3194c687 Vincent Cuissard 2015-10-26  281  		}
3194c687 Vincent Cuissard 2015-10-26  282  		skb_pull(skb, 1);
3194c687 Vincent Cuissard 2015-10-26  283  		memcpy(&len, skb->data, 2);
3194c687 Vincent Cuissard 2015-10-26  284  		skb_pull(skb, 2);
3194c687 Vincent Cuissard 2015-10-26  285  		memcpy(&comp_len, skb->data, 2);
3194c687 Vincent Cuissard 2015-10-26  286  		skb_pull(skb, 2);
3194c687 Vincent Cuissard 2015-10-26 @287  		len = get_unaligned_le16(&len);
3194c687 Vincent Cuissard 2015-10-26  288  		comp_len = get_unaligned_le16(&comp_len);
3194c687 Vincent Cuissard 2015-10-26  289  		if (((~len) & 0xFFFF) != comp_len) {
3194c687 Vincent Cuissard 2015-10-26  290  			nfc_err(priv->dev, "bad len complement: %x %x %x",

:::::: The code at line 287 was first introduced by commit
:::::: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware download support

:::::: TO: Vincent Cuissard <cuissard@marvell.com>
:::::: CC: Samuel Ortiz <sameo@linux.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/gzip, Size: 27223 bytes --]

  reply	other threads:[~2017-01-09  0:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  0:19 [PATCH] nfc: don't be making arch specific unaligned decisions at driver level Paul Gortmaker
2017-01-09  0:47 ` kbuild test robot [this message]
2017-01-09  0:56 ` kbuild test robot
2017-01-09 17:52   ` [PATCH v2] " Paul Gortmaker
2017-03-28 22:55     ` Paul Gortmaker
2017-03-29  6:51       ` Samuel Ortiz
2017-04-01 22:22     ` Samuel Ortiz
2017-04-03 17:27       ` Paul Gortmaker
2017-04-04  1:55       ` Paul Gortmaker

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=201701090805.NVKb2IVs%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=linux-ia64@vger.kernel.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