From: Max Krasnyansky <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, menage@google.com,
a.p.zijlstra@chello.nl, vegard.nossum@gmail.com
Subject: Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling
Date: Thu, 31 Jul 2008 18:58:53 -0700 [thread overview]
Message-ID: <48926DDD.9030003@qualcomm.com> (raw)
In-Reply-To: <20080731151421.bb4af984.pj@sgi.com>
Paul Jackson wrote:
> Max,
>
> What kernel version was this patch against?
>
> I've tried 2.6.27-rc1-mm1, 2.6.27-rc1, and 2.6.26,
> and it doesn't apply cleanly on any of them.
>
It was on top of the then latest -tip.
I believe it git automerged it with no conflicts on top of .27-rc1.
I'll resend updated version a bit later.
Max
next prev parent reply other threads:[~2008-08-01 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 22:33 [PATCH] cpuset: Rework sched domains and CPU hotplug handling Max Krasnyansky
2008-07-26 19:40 ` Max Krasnyansky
2008-07-28 14:07 ` Ingo Molnar
2008-07-29 6:40 ` Peter Zijlstra
2008-07-29 16:59 ` Max Krasnyansky
2008-07-31 20:14 ` Paul Jackson
2008-08-01 1:58 ` Max Krasnyansky [this message]
2008-08-01 6:49 ` 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=48926DDD.9030003@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=vegard.nossum@gmail.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