From: kbuild test robot <lkp@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: kbuild-all@01.org, axboe@kernel.dk,
Jeff Moyer <jmoyer@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Jan Kara <jack@suse.com>
Subject: Re: [PATCH 4/4] cfq-iosched: Allow parent cgroup to preempt its child
Date: Thu, 26 Nov 2015 04:24:23 +0800 [thread overview]
Message-ID: <201511260459.yzWTWt80%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448461351-22481-5-git-send-email-jack@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi Jan,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.4-rc2 next-20151124]
url: https://github.com/0day-ci/linux/commits/Jan-Kara/SYNC_NOIDLE-preemption-for-ancestor-cgroups/20151125-222645
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: i386-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "cgroup_is_descendant" undefined!
---
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: 52591 bytes --]
next prev parent reply other threads:[~2015-11-25 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 14:22 [PATCH 0/4] SYNC_NOIDLE preemption for ancestor cgroups Jan Kara
2015-11-25 14:22 ` [PATCH 1/4] cfq-iosched: Don't group_idle if cfqq has big thinktime Jan Kara
2015-11-25 14:22 ` [PATCH 2/4] cfq-iosched: Reorder checks in cfq_should_preempt() Jan Kara
2015-11-25 14:22 ` [PATCH 3/4] cfq-iosched: Allow sync noidle workloads to preempt each other Jan Kara
2015-11-25 14:22 ` [PATCH 4/4] cfq-iosched: Allow parent cgroup to preempt its child Jan Kara
2015-11-25 20:24 ` kbuild test robot [this message]
2015-11-26 13:22 ` Jan Kara
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=201511260459.yzWTWt80%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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®