From: kbuild test robot <lkp@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: linux-next: manual merge of the akpm-current tree with the block tree
Date: Mon, 2 Nov 2015 00:05:26 +0800 [thread overview]
Message-ID: <201511020018.0nqlBQpz%fengguang.wu@intel.com> (raw)
In-Reply-To: <20151102025125.0f335513@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
Hi Stephen,
[auto build test ERROR on block/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Stephen-Rothwell/linux-next-manual-merge-of-the-akpm-current-tree-with-the-block-tree/20151101-235406
config: x86_64-randconfig-x019-201544 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
block/blk-core.c: In function 'blk_queue_enter':
>> block/blk-core.c:641:8: error: implicit declaration of function 'gfpflags_allow_blocking' [-Werror=implicit-function-declaration]
if (!gfpflags_allow_blocking(gfp))
^
In file included from include/linux/linkage.h:4:0,
from include/linux/kernel.h:6,
from block/blk-core.c:14:
block/blk-core.c: In function 'generic_make_request':
>> block/blk-core.c:2041:33: error: '__GFP_RECLAIM' undeclared (first use in this function)
if (likely(blk_queue_enter(q, __GFP_RECLAIM) == 0)) {
^
include/linux/compiler.h:165:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
block/blk-core.c:2041:33: note: each undeclared identifier is reported only once for each function it appears in
if (likely(blk_queue_enter(q, __GFP_RECLAIM) == 0)) {
^
include/linux/compiler.h:165:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
cc1: some warnings being treated as errors
vim +/gfpflags_allow_blocking +641 block/blk-core.c
635 while (true) {
636 int ret;
637
638 if (percpu_ref_tryget_live(&q->q_usage_counter))
639 return 0;
640
> 641 if (!gfpflags_allow_blocking(gfp))
642 return -EBUSY;
643
644 ret = wait_event_interruptible(q->mq_freeze_wq,
---
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: 25667 bytes --]
next prev parent reply other threads:[~2015-11-01 16:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 15:51 linux-next: manual merge of the akpm-current tree with the block tree Stephen Rothwell
2015-11-01 16:04 ` kbuild test robot
2015-11-01 16:05 ` kbuild test robot [this message]
2015-11-01 18:38 ` Mel Gorman
2015-11-01 21:51 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 5:40 Stephen Rothwell
2021-04-07 9:18 Stephen Rothwell
2021-03-18 6:17 Stephen Rothwell
2021-03-18 17:54 ` Shakeel Butt
2021-03-18 18:19 ` Jens Axboe
2020-11-17 5:05 Stephen Rothwell
2020-10-15 6:27 Stephen Rothwell
2020-09-25 9:57 Stephen Rothwell
2019-05-03 9:10 Stephen Rothwell
2019-05-03 12:35 ` Amir Goldstein
2018-10-02 7:21 Stephen Rothwell
2018-08-13 7:51 Stephen Rothwell
2018-08-02 8:31 Stephen Rothwell
2018-03-19 6:36 Stephen Rothwell
2016-07-13 6:14 Stephen Rothwell
2016-07-13 16:31 ` Jens Axboe
2015-12-07 8:12 Stephen Rothwell
2015-12-07 19:44 ` Andrew Morton
2015-12-07 20:24 ` Stephen Rothwell
2015-01-21 7:14 Stephen Rothwell
2014-07-02 6:06 Stephen Rothwell
2013-11-05 6:29 Stephen Rothwell
2013-11-05 6:25 Stephen Rothwell
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=201511020018.0nqlBQpz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=sfr@canb.auug.org.au \
/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).