From: kernel test robot <lkp@intel.com>
To: "hongxu.zhao" <hongxu.zhao@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@lists.01.org,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
wsd_upstream@mediatek.com, Weiqi Fu <weiqi.fu@mediatek.com>,
Hongxu Zhao <hongxu.zhao@mediatek.com>,
open list <linux-kernel@vger.kernel.org>,
Cunliang Du <cunliang.du@mediatek.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Zhen jiang <zhen.jiang@mediatek.com>
Subject: Re: [PATCH] staging: Add Mediatek High Frequency Manager Framework
Date: Tue, 4 Aug 2020 18:35:00 +0800 [thread overview]
Message-ID: <202008041829.0pFOJzee%lkp@intel.com> (raw)
In-Reply-To: <20200804075339.9820-1-hongxu.zhao@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
Hi "hongxu.zhao",
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
url: https://github.com/0day-ci/linux/commits/hongxu-zhao/staging-Add-Mediatek-High-Frequency-Manager-Framework/20200804-155814
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 5bbd90550da8f7bdac769b5825597e67183c9411
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
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
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/kernel.h:11,
from drivers/staging/hf_manager/core/hf_manager.c:9:
drivers/staging/hf_manager/core/hf_manager.c: In function 'hf_manager_io_schedule':
>> include/linux/compiler.h:301:1: error: expected expression before 'do'
301 | do { \
| ^~
arch/alpha/include/asm/atomic.h:34:27: note: in expansion of macro 'WRITE_ONCE'
34 | #define atomic64_set(v,i) WRITE_ONCE((v)->counter, (i))
| ^~~~~~~~~~
drivers/staging/hf_manager/core/hf_manager.h:145:40: note: in expansion of macro 'atomic64_set'
145 | #define set_interrupt_timestamp(m, t) (atomic64_set(&m->timestamp, t))
| ^~~~~~~~~~~~
drivers/staging/hf_manager/core/hf_manager.c:171:2: note: in expansion of macro 'set_interrupt_timestamp'
171 | set_interrupt_timestamp(manager, timestamp);
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/do +301 include/linux/compiler.h
a5460b5e5fb826 Will Deacon 2019-12-16 299
9e343b467c7037 Will Deacon 2019-12-13 300 #define WRITE_ONCE(x, val) \
9e343b467c7037 Will Deacon 2019-12-13 @301 do { \
9e343b467c7037 Will Deacon 2019-12-13 302 compiletime_assert_rwonce_type(x); \
44b97dccb2291a Marco Elver 2020-05-21 303 __WRITE_ONCE(x, val); \
9e343b467c7037 Will Deacon 2019-12-13 304 } while (0)
9e343b467c7037 Will Deacon 2019-12-13 305
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65090 bytes --]
prev parent reply other threads:[~2020-08-04 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200804075339.9820-1-hongxu.zhao@mediatek.com>
2020-08-04 8:11 ` [PATCH] staging: Add Mediatek High Frequency Manager Framework Greg Kroah-Hartman
[not found] ` <1596702748.6258.3.camel@mbjsdccf07>
2020-08-06 10:53 ` Greg Kroah-Hartman
[not found] ` <1596781829.14444.17.camel@mbjsdccf07>
2020-08-07 6:45 ` Greg Kroah-Hartman
2020-08-04 10:35 ` kernel test robot [this message]
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=202008041829.0pFOJzee%lkp@intel.com \
--to=lkp@intel.com \
--cc=cunliang.du@mediatek.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hongxu.zhao@mediatek.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=weiqi.fu@mediatek.com \
--cc=wsd_upstream@mediatek.com \
--cc=zhen.jiang@mediatek.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