From: kbuild test robot <lkp@intel.com>
To: George Hilliard <thirtythreeforty@gmail.com>
Cc: kbuild-all@01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, NeilBrown <neil@brown.name>,
George Hilliard <thirtythreeforty@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: Mediatek: Use individual config flags in Makefile
Date: Wed, 16 Jan 2019 12:43:21 +0800 [thread overview]
Message-ID: <201901161202.Clg8Z9Jg%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190115172916.26937-1-thirtythreeforty@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]
Hi George,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[cannot apply to v5.0-rc2 next-20190115]
[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/George-Hilliard/staging-Mediatek-Use-individual-config-flags-in-Makefile/20190116-084915
config: x86_64-randconfig-e0-201902 (attached as .config)
compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/staging/mt7621-mmc/dbg.c:51:
drivers/staging/mt7621-mmc/mt6575_sd.h: In function 'sdr_set_bits':
drivers/staging/mt7621-mmc/mt6575_sd.h:459:12: error: implicit declaration of function 'readl'; did you mean 'd_real'? [-Werror=implicit-function-declaration]
u32 val = readl(reg);
^~~~~
d_real
>> drivers/staging/mt7621-mmc/mt6575_sd.h:462:2: error: implicit declaration of function 'writel'; did you mean 'wrmsrl'? [-Werror=implicit-function-declaration]
writel(val, reg);
^~~~~~
wrmsrl
cc1: some warnings being treated as errors
vim +462 drivers/staging/mt7621-mmc/mt6575_sd.h
8b634a9c John Crispin 2018-03-15 456
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 457 static inline void sdr_set_bits(void __iomem *reg, u32 bs)
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 458 {
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 @459 u32 val = readl(reg);
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 460
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 461 val |= bs;
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 @462 writel(val, reg);
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 463 }
0b78f05d Christian Lütke-Stetzkamp 2018-04-24 464
:::::: The code at line 462 was first introduced by commit
:::::: 0b78f05d510b01e353481f5bccb63661d2cb5c32 staging: mt7621-mmc: Correct datatypes for io and sanitize io access
:::::: TO: Christian Lütke-Stetzkamp <christian@lkamp.de>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
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: 32442 bytes --]
next prev parent reply other threads:[~2019-01-16 4:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACmrr9gHucWaWtz07kQms6AsquLKAHbK+_Q0kF=92RGo6HmAFA@mail.gmail.com>
2019-01-11 0:43 ` [PATCH v2 1/2] Move ralink-gdma to its own directory thirtythreeforty
2019-01-11 0:43 ` [PATCH v2 2/2] Mediatek staging: Use individual config flags in Makefile thirtythreeforty
2019-01-15 15:30 ` [PATCH v2 2/2] staging: Mediatek: " Greg Kroah-Hartman
2019-01-15 17:02 ` [PATCH v3] " George Hilliard
2019-01-15 17:20 ` Greg Kroah-Hartman
2019-01-15 17:29 ` [PATCH v4] " George Hilliard
2019-01-15 17:43 ` Greg Kroah-Hartman
2019-01-16 6:48 ` [PATCH v5] " George Hilliard
2019-01-16 4:43 ` kbuild test robot [this message]
2019-01-15 17:32 ` [PATCH v3] " George Hilliard
2019-01-11 1:21 ` [PATCH v2 1/2] Move ralink-gdma to its own directory NeilBrown
2019-01-11 2:13 ` George Hilliard
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=201901161202.Clg8Z9Jg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=thirtythreeforty@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;
as well as URLs for NNTP newsgroup(s).