From: Ingo Molnar <mingo@elte.hu>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched: trivial fix for incorrect comments
Date: Mon, 22 Sep 2008 13:00:49 +0200 [thread overview]
Message-ID: <20080922110049.GA5987@elte.hu> (raw)
In-Reply-To: <48D3C9FF.20504@nortel.com>
* Chris Friesen <cfriesen@nortel.com> wrote:
> From: Chris Friesen <cfriesen@nortel.com>
>
> A couple of the comments for the conditional definitions in sched.c are
> incorrect. Here's a trivial patch fixing them up.
looks good to me, but the patch is whitespace corrupted. Please see
Documentation/email-clients.txt about how to send plain-text patches.
Ingo
next prev parent reply other threads:[~2008-09-22 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 15:49 [patch] sched: trivial fix for incorrect comments Chris Friesen
2008-09-22 11:00 ` Ingo Molnar [this message]
2008-09-23 16:08 ` Chris Friesen
2008-09-27 18:10 ` Ingo Molnar
2008-09-27 18:19 ` Peter Zijlstra
2008-09-27 18:22 ` Ingo Molnar
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=20080922110049.GA5987@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.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 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.