mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Yifeng Li <tomli@tomli.me>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
	linux-mips@vger.kernel.org, Yifeng Li <tomli@tomli.me>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Huacai Chen <chenhc@lemote.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paul.burton@mips.com>,
	James Hogan <jhogan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] mfd: yeeloong_kb3310b: support KB3310B EC for Lemote Yeeloong laptops.
Date: Mon, 4 Mar 2019 08:37:28 +0800	[thread overview]
Message-ID: <201903040851.4ZDLoz8h%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190302175334.5103-2-tomli@tomli.me>

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

Hi Yifeng,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.0-rc8]
[cannot apply to next-20190301]
[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/Yifeng-Li/Preliminary-Platform-Driver-Support-for-Lemote-Yeeloong-Laptops/20190304-005203
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 8.2.0-11) 8.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=8.2.0 make.cross ARCH=powerpc 

All errors (new ones prefixed by >>):

   drivers//mfd/yeeloong_kb3310b.c: In function 'kb3310b_read':
>> drivers//mfd/yeeloong_kb3310b.c:70:2: error: implicit declaration of function 'outb'; did you mean 'mftb'? [-Werror=implicit-function-declaration]
     outb((reg & 0xff00) >> 8, KB3310B_IO_PORT_HIGH);
     ^~~~
     mftb
   drivers//mfd/yeeloong_kb3310b.c:72:8: error: implicit declaration of function 'inb' [-Werror=implicit-function-declaration]
     val = inb(KB3310B_IO_PORT_DATA);
           ^~~
   cc1: some warnings being treated as errors

vim +70 drivers//mfd/yeeloong_kb3310b.c

    62	
    63	u8 kb3310b_read(u16 reg)
    64	{
    65		unsigned long flags;
    66		u8 val;
    67	
    68		spin_lock_irqsave(&kb3310b_index_lock, flags);
    69	
  > 70		outb((reg & 0xff00) >> 8, KB3310B_IO_PORT_HIGH);
    71		outb((reg & 0x00ff), KB3310B_IO_PORT_LOW);
    72		val = inb(KB3310B_IO_PORT_DATA);
    73	
    74		spin_unlock_irqrestore(&kb3310b_index_lock, flags);
    75	
    76		return val;
    77	}
    78	EXPORT_SYMBOL_GPL(kb3310b_read);
    79	

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

  parent reply	other threads:[~2019-03-04  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 17:53 [PATCH 0/7] Preliminary Platform Driver Support for Lemote Yeeloong Laptops Yifeng Li
2019-03-02 17:53 ` [PATCH 1/7] mfd: yeeloong_kb3310b: support KB3310B EC for Lemote Yeeloong laptops Yifeng Li
     [not found]   ` <201903040432.qyPxOrOQ%fengguang.wu@intel.com>
2019-03-04  0:24     ` Tom Li
2019-03-04  0:37   ` kbuild test robot [this message]
2019-03-04 10:14     ` Lee Jones
2019-03-04 12:19       ` Tom Li
2019-03-02 17:53 ` [PATCH 2/7] mips: loongson64: select MFD_YEELOONG_KB3310B for LEMOTE_MACH2F Yifeng Li
2019-03-02 17:53 ` [PATCH 3/7] mips: loongson64: remove ec_kb3310b.c, use MFD driver Yifeng Li
2019-03-02 17:53 ` [PATCH 4/7] mips: loongson64: remove yeeloong_report_lid_status from pm.c Yifeng Li
2019-03-02 17:53 ` [PATCH 5/7] mips: loongson64: register per-board platform drivers for lemote-2f Yifeng Li
2019-03-02 17:53 ` [PATCH 6/7] mips: loongson64: Support System Control Interrupts for Lemote Yeeloong Yifeng Li
2019-03-02 17:53 ` [PATCH 7/7] MAINTAINERS: add myself as a maintainer of MIPS/Loongson2 platform code Yifeng Li

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=201903040851.4ZDLoz8h%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=chenhc@lemote.com \
    --cc=jhogan@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kbuild-all@01.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=tomli@tomli.me \
    /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®