From: Kenny Yu <kennyyu@fb.com>
To: <tj@kernel.org>, <lizefan@huawei.com>, <hannes@cmpxchg.org>,
<cyphar@cyphar.com>
Cc: <kennyyu@fb.com>, <cgroups@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-team@fb.com>
Subject: [PATCH] cgroup: Use lld instead of ld when printing pids controller events_limit
Date: Tue, 21 Jun 2016 11:55:35 -0700 [thread overview]
Message-ID: <1466535335-3715145-1-git-send-email-kennyyu@fb.com> (raw)
The `events_limit` variable needs to be formatted with %lld and not %ld.
This fixes the following warning discovered by kbuild test robot:
kernel/cgroup_pids.c: In function 'pids_events_show':
kernel/cgroup_pids.c:313:24: warning: format '%ld' expects argument of type
'long int', but argument 3 has type 'long long int' [-Wformat=]
seq_printf(sf, "max %ld\n", atomic64_read(&pids->events_limit));
^
Signed-off-by: Kenny Yu <kennyyu@fb.com>
---
kernel/cgroup_pids.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cgroup_pids.c b/kernel/cgroup_pids.c
index bd2490b..1777d03 100644
--- a/kernel/cgroup_pids.c
+++ b/kernel/cgroup_pids.c
@@ -310,7 +310,7 @@ static int pids_events_show(struct seq_file *sf, void *v)
{
struct pids_cgroup *pids = css_pids(seq_css(sf));
- seq_printf(sf, "max %ld\n", atomic64_read(&pids->events_limit));
+ seq_printf(sf, "max %lld\n", atomic64_read(&pids->events_limit));
return 0;
}
--
2.8.0.rc2
next reply other threads:[~2016-06-21 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 18:55 Kenny Yu [this message]
2016-06-21 19:09 ` [PATCH] cgroup: Use lld instead of ld when printing pids controller events_limit Tejun Heo
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=1466535335-3715145-1-git-send-email-kennyyu@fb.com \
--to=kennyyu@fb.com \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--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