From: Randy Dunlap <randy.dunlap@oracle.com>
To: Venkatesh Pallipadi <venki@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jaswinder Singh <jaswinderlinux@gmail.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] Fix linux-next warning from abb74cef
Date: Mon, 31 Jan 2011 12:25:28 -0800 [thread overview]
Message-ID: <20110131122528.050a4c23.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1296505006-26660-1-git-send-email-venki@google.com>
On Mon, 31 Jan 2011 12:16:46 -0800 Venkatesh Pallipadi wrote:
> Thanks. Updated to address comments from Randy.
>
> Yes. Patch below should fix the problem.
>
> Fix below warning -
> Introduced by commit abb74cefa9c682fb38ba86c17ca3c86fed6cc464 ("sched:
> Export ns irqtimes through /proc/stat").
Thanks, Venki.
Maybe next time we can even get a descriptive $subject. ;)
(I'm not requesting that you resend this patch.)
> After merging the tip tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> kernel/sched.c:3719: warning: 'irqtime_account_idle_ticks' defined but not used
> kernel/sched.c:3720: warning: 'irqtime_account_process_tick' defined but not used
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Venkatesh Pallipadi <venki@google.com>
> ---
> kernel/sched.c | 64 ++++++++++++++++++++++++++++----------------------------
> 1 files changed, 32 insertions(+), 32 deletions(-)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-01-31 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 4:27 linux-next: build warnings after merge of the tip tree Stephen Rothwell
2011-01-31 5:08 ` Jaswinder Singh
2011-01-31 19:12 ` [PATCH] Fix linux-next warning from abb74cef Venkatesh Pallipadi
2011-01-31 19:38 ` Randy Dunlap
2011-01-31 20:16 ` Venkatesh Pallipadi
2011-01-31 20:25 ` Randy Dunlap [this message]
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=20110131122528.050a4c23.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=hpa@zytor.com \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
/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