mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peng Sun <sironhide0null@gmail.com>
Cc: kbuild-all@01.org, liodot@gmail.com, charrer@alacritech.com,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	Peng Sun <sironhide0null@gmail.com>
Subject: Re: [PATCH 1/1] staging: slicoss: slicoss.c: fix different address space sparse warnings
Date: Tue, 13 Sep 2016 11:57:39 +0800	[thread overview]
Message-ID: <201609131117.HQilr7GR%fengguang.wu@intel.com> (raw)
In-Reply-To: <1473736984-6859-2-git-send-email-sironhide0null@gmail.com>

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

Hi Peng,

[auto build test ERROR on staging/staging-testing]
[also build test ERROR on next-20160912]
[cannot apply to v4.8-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Peng-Sun/staging-slicoss-slicoss-c-fix-different-address-space-sparse-warnings/20160913-112524
config: i386-randconfig-x010-201637 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   In file included from drivers/staging/slicoss/slicoss.c:97:0:
   drivers/staging/slicoss/slicoss.c: In function 'slic_upr_request_complete':
>> drivers/staging/slicoss/slicoss.c:1022:5: error: implicit declaration of function 'readq' [-Werror=implicit-function-declaration]
        readq((char __iomem *)stats +
        ^
   drivers/staging/slicoss/slic.h:552:19: note: in definition of macro 'UPDATE_STATS_GB'
     (largestat) += ((newstat) - (oldstat));                          \
                      ^~~~~~~
   cc1: some warnings being treated as errors

vim +/readq +1022 drivers/staging/slicoss/slicoss.c

  1016				dev_err(&adapter->netdev->dev,
  1017					"SLIC_UPR_STATS command failed isr[%x]\n", isr);
  1018				break;
  1019			}
  1020	
  1021			UPDATE_STATS_GB(stst->tcp.xmit_tcp_segs,
> 1022					readq((char __iomem *)stats +
  1023					      offsetof(struct slic_stats,
  1024						       xmit_tcp_segs)),
  1025					old->xmit_tcp_segs);

---
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: 28414 bytes --]

  reply	other threads:[~2016-09-13  3:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  3:23 [PATCH 0/1] staging: slicoss: slicoss: fix " Peng Sun
2016-09-13  3:23 ` [PATCH 1/1] staging: slicoss: slicoss.c: fix different address space " Peng Sun
2016-09-13  3:57   ` kbuild test robot [this message]
2016-09-13  6:01   ` Greg KH

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=201609131117.HQilr7GR%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=charrer@alacritech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liodot@gmail.com \
    --cc=sironhide0null@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®