From: yuankuiz@codeaurora.org
To: cgroups@vger.kernel.org, tj@kernel.org, lizefan@huawei.com,
hannes@cmpxchg.org
Cc: linux-kernel@vger.kernel.org, pkondeti@codeaurora.org,
cgroups-owner@vger.kernel.org
Subject: Re: [PATCH]cgroup: __cpuset_node_allowed return bool
Date: Sat, 24 Mar 2018 13:05:50 +0800 [thread overview]
Message-ID: <0fee75e4a1b12f5fca30e04306a95788@codeaurora.org> (raw)
In-Reply-To: <d2f9fe6096235032f445ab88e562560f@codeaurora.org>
From 304cec1cc42255fbd9e231a810f4eea20ab74b90 Mon Sep 17 00:00:00 2001
From: John Zhao <yuankuiz@codeaurora.org>
Date: Sat, 24 Mar 2018 13:01:32 +0800
Subject: [PATCH] cgroup: __cpuset_node_allowed return bool
as a bool, __cpuset_node_allowed(...) return should be bool.
Signed-off-by: John Zhao <yuankuiz@codeaurora.org>
---
kernel/cgroup/cpuset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
index b42037e..42338b7 100644
--- a/kernel/cgroup/cpuset.c
+++ b/kernel/cgroup/cpuset.c
@@ -2552,7 +2552,7 @@ static struct cpuset
*nearest_hardwall_ancestor(struct cpuset *cs)
bool __cpuset_node_allowed(int node, gfp_t gfp_mask)
{
struct cpuset *cs; /* current cpuset ancestors */
- int allowed; /* is allocation in zone z allowed? */
+ bool allowed; /* is allocation in zone z allowed? */
unsigned long flags;
if (in_interrupt())
--
2.7.4
next prev parent reply other threads:[~2018-03-24 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 4:56 [PATCH]cgroup: __cpuset_node_allowed return bool yuankuiz
2018-03-24 5:05 ` yuankuiz [this message]
2018-03-26 14:12 ` Tejun Heo
2018-03-26 14:20 ` yuankuiz
2018-03-26 14:25 ` Tejun Heo
2018-03-26 14:37 ` yuankuiz
2018-03-26 14:41 ` yuankuiz
2018-03-27 16:45 ` yuankuiz
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=0fee75e4a1b12f5fca30e04306a95788@codeaurora.org \
--to=yuankuiz@codeaurora.org \
--cc=cgroups-owner@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pkondeti@codeaurora.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;
as well as URLs for NNTP newsgroup(s).