All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Langsdorf, Mark" <mark.langsdorf@amd.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Gautham R Shenoy <ego@in.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Regression in 2.6.27-rc1 for set_cpus_allowed_ptr
Date: Mon, 11 Aug 2008 15:49:55 -0700	[thread overview]
Message-ID: <48A0C213.4090305@qualcomm.com> (raw)
In-Reply-To: <20080811224636.GA25577@elte.hu>



Ingo Molnar wrote:
> * Max Krasnyansky <maxk@qualcomm.com> wrote:
> 
>>> And I was hoping to do -rc3 today. Can I please have pull-requests for the 
>>> appropriate urgent scheduler/x86 fixes? Or should I just take these as 
>>> patches?
>> It'd be nice if -rc3 included my cpuset patch so that we could put circular
>> locking issues in the cpu hotplug path to the rest.
>> Ingo, I'm talking about this:
>> 	[PATCH] cpuset: Rework sched domains and CPU hotplug handling (take 4)
> 
> the latest (-v4) version of the patch was submitted just half an hour 
> ago and it's rather large/complex, with a few unrelated changes 
> (whitespace, etc.) mixed in as well. I'd like to wait for Paul's final 
> ack for -v4 (he has already agreed with the approach in general), and 
> wanted to have it tested myself as well, at least minimally.

Fair enough.

btw Whitespace and other cosmetic changes were requested by reviewers.

Max

  reply	other threads:[~2008-08-11 22:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 19:44 Regression in 2.6.27-rc1 for set_cpus_allowed_ptr Langsdorf, Mark
2008-08-08 21:03 ` Rafael J. Wysocki
2008-08-08 21:31   ` Dmitry Adamushko
2008-08-11 12:30     ` Ingo Molnar
2008-08-11 14:01       ` Langsdorf, Mark
2008-08-11 14:20         ` Ingo Molnar
2008-08-11 14:28       ` Dmitry Adamushko
2008-08-11 22:03       ` Linus Torvalds
2008-08-11 22:10         ` Ingo Molnar
2008-08-11 22:14         ` Max Krasnyansky
2008-08-11 22:46           ` Ingo Molnar
2008-08-11 22:49             ` Max Krasnyansky [this message]
2008-08-11 22:55               ` 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=48A0C213.4090305@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.adamushko@gmail.com \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --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 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.