All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Cong Ding <dinggnu@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: fix compilation warning
Date: Sat, 19 Jan 2013 11:26:34 -0800	[thread overview]
Message-ID: <50FAF36A.6000205@xenotime.net> (raw)
In-Reply-To: <CAM3j68rOMRdrovAkWdwfB477W+efMC1uGkbHNjz+kRz4LMaXag@mail.gmail.com>

On 01/18/13 12:47, Cong Ding wrote:
> Is this patch still queued or...?
> 
> - cong

ping.
Can we get this patch or something similar merged, please?


> On Wed, Dec 5, 2012 at 6:10 PM, Cong Ding <dinggnu@gmail.com> wrote:
>> the following compilation warning is caused by Commit-ID:
>> c566e8e9e44b72b53091da20e2dedefc730f2ee2
>>
>> kernel/sched/debug.c: In function ‘print_cfs_rq’:
>> kernel/sched/debug.c:225:2: warning: format ‘%ld’ expects argument of type
>> ‘long int’, but argument 4 has type ‘long long int’ [-Wformat]
>> kernel/sched/debug.c:225:2: warning: format ‘%ld’ expects argument of type
>> ‘long int’, but argument 3 has type ‘long long int’ [-Wformat]
>>
>> where function atomic64_read returns long long int, but %ld was used in the
>> printf
>>
>> Signed-off-by: Cong Ding <dinggnu@gmail.com>
>> ---
>>  kernel/sched/debug.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c
>> index 2cd3c1b..83ec463 100644
>> --- a/kernel/sched/debug.c
>> +++ b/kernel/sched/debug.c
>> @@ -222,7 +222,7 @@ void print_cfs_rq(struct seq_file *m, int cpu, struct cfs_rq *cfs_rq)
>>                         cfs_rq->runnable_load_avg);
>>         SEQ_printf(m, "  .%-30s: %lld\n", "blocked_load_avg",
>>                         cfs_rq->blocked_load_avg);
>> -       SEQ_printf(m, "  .%-30s: %ld\n", "tg_load_avg",
>> +       SEQ_printf(m, "  .%-30s: %lld\n", "tg_load_avg",
>>                         atomic64_read(&cfs_rq->tg->load_avg));
>>         SEQ_printf(m, "  .%-30s: %lld\n", "tg_load_contrib",
>>                         cfs_rq->tg_load_contrib);
>> --


-- 
~Randy

  reply	other threads:[~2013-01-19 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 17:10 [PATCH] sched: fix compilation warning Cong Ding
2013-01-18 20:47 ` Cong Ding
2013-01-19 19:26   ` Randy Dunlap [this message]
2013-01-27 13:59     ` [PATCH resend] " Cong Ding

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=50FAF36A.6000205@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=dinggnu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.