The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pranith Kumar D <pranith-kumar_d@mentor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CFS: sched-design-CFS.txt - ambiguity about leftmost and some formatting
Date: Tue, 22 May 2007 12:48:13 +0200	[thread overview]
Message-ID: <20070522104813.GA11260@elte.hu> (raw)
In-Reply-To: <20070522101437.GA32528@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> * Pranith Kumar D <pranith-kumar_d@mentor.com> wrote:
> 
> > The document is very clear and explains the basic mechanism of CFS 
> > very well. But, i find that the descriptions are a bit up and down. I 
> > mean, u use leftmost and rightmost before mentioning that CFS uses 
> > rbtree.( which comes much later).
> > 
> > In the following patch I mentioned the rbtree, the first time you 
> > talked about 'leftmost'. Also i did some basic formatting. Hope its 
> > not a pain. :)
> 
> thanks - but the patch is whitespace damaged and wont apply:
> 
> patch: **** malformed patch at line 10: 80% of CFS's design can be 
> 
> that's because the leading space got stripped by your mailer.

i have applied your last resent patch and it should show up in -v14. 
Thanks!

	Ingo

      parent reply	other threads:[~2007-05-22 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22  6:50 [PATCH] CFS: sched-design-CFS.txt - ambiguity about leftmost Pranith Kumar D
2007-05-22  8:30 ` Ingo Molnar
2007-05-22  9:28   ` [PATCH] CFS: sched-design-CFS.txt - ambiguity about leftmost and some formatting Pranith Kumar D
2007-05-22 10:14     ` Ingo Molnar
     [not found]       ` <4652C379.3050801@mentorg.com>
     [not found]         ` <20070522102430.GA2344@elte.hu>
2007-05-22 10:44           ` Pranith Kumar D
2007-05-22 10:48       ` Ingo Molnar [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=20070522104813.GA11260@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranith-kumar_d@mentor.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