From: Meelis Roos <mroos@linux.ee>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Warnings from sched_debug.c
Date: Fri, 21 Dec 2007 14:31:39 +0200 (EET) [thread overview]
Message-ID: <Pine.SOC.4.64.0712211423400.24473@math.ut.ee> (raw)
In-Reply-To: <20071221110336.GB29047@elte.hu>
> it should be harmless. Does the patch below fix the warnings?
Yes, the warnings are gone, thanks!
However, I found another somewhat strange thing while testing it -
touching kernels/sched_debug.c does not cause a recompile since
sched_debug.c is only #included from sched.c. Found it because I was
looking for sched_debug.o recompile.
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2007-12-21 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 10:18 Warnings from sched_debug.c Meelis Roos
2007-12-21 11:03 ` Ingo Molnar
2007-12-21 12:31 ` Meelis Roos [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=Pine.SOC.4.64.0712211423400.24473@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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