From: Ingo Molnar <mingo@elte.hu>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Paul Jackson <pj@sgi.com>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
gregkh@suse.de, rusty@rustcorp.com.au
Subject: Re: [git pull] CPU isolation extensions (updated)
Date: Wed, 13 Feb 2008 11:58:04 +0100 [thread overview]
Message-ID: <20080213105804.GE32241@elte.hu> (raw)
In-Reply-To: <47AE76B8.6060304@qualcomm.com>
* Max Krasnyansky <maxk@qualcomm.com> wrote:
> Ingo said a few different things (a bit too large to quote).
[...]
> And at the end he said:
> > Also, i'd not mind some test-coverage in sched.git as well.
> I far as I know "do not mind" does not mean "must go to" ;-). [...]
the CPU isolation related patches have typically flown through
sched.git/sched-devel.git, so yes, you can take my "i'd not mind"
comment as "i'd not mind it at all". That's the tree that all the folks
who deal with this (such as Paul) are following. So lets go via the
normal contribution cycle and let this trickle through with all the
scheduler folks? I'd say 2.6.26 would be a tentative target, if it holds
up to scrutiny in sched-devel.git (both testing and review wise). And
because Andrew tracks sched-devel.git it will thus show up in -mm too.
Ingo
next prev parent reply other threads:[~2008-02-13 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 3:07 [git pull] CPU isolation extensions (updated) Max Krasnyansky
2008-02-10 3:21 ` Paul Jackson
2008-02-10 3:59 ` Max Krasnyansky
2008-02-13 10:58 ` Ingo Molnar [this message]
2008-02-13 17:18 ` Max Krasnyansky
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=20080213105804.GE32241@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=pj@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox