Re: [patch 2/5] sched: NULL domains

Ingo Molnar wrote: * Ingo Molnar <[EMAIL PROTECTED]> wrote: * Nick Piggin <[EMAIL PROTECTED]> wrote: 2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no

Re: [patch 2/5] sched: NULL domains

Ingo Molnar wrote: * Ingo Molnar [EMAIL PROTECTED] wrote: * Nick Piggin [EMAIL PROTECTED] wrote: 2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no

Re: [patch 2/5] sched: NULL domains

* Nick Piggin <[EMAIL PROTECTED]> wrote: > 2/5 > The previous patch fixed the last 2 places that directly access a > runqueue's sched-domain and assume it cannot be NULL. > > We can now use a NULL domain instead of a dummy domain to signify > no balancing is to happen. No functional changes. >

Re: [patch 2/5] sched: NULL domains

* Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Nick Piggin <[EMAIL PROTECTED]> wrote: > > > 2/5 > > > The previous patch fixed the last 2 places that directly access a > > runqueue's sched-domain and assume it cannot be NULL. > > > > We can now use a NULL domain instead of a dummy domain to

[patch 2/5] sched: NULL domains

2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no balancing is to happen. No functional changes. Signed-off-by: Nick Piggin <[EMAIL PROTECTED]> Index:

[patch 2/5] sched: NULL domains

2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no balancing is to happen. No functional changes. Signed-off-by: Nick Piggin [EMAIL PROTECTED] Index:

Re: [patch 2/5] sched: NULL domains

* Ingo Molnar [EMAIL PROTECTED] wrote: * Nick Piggin [EMAIL PROTECTED] wrote: 2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no

Re: [patch 2/5] sched: NULL domains

* Nick Piggin [EMAIL PROTECTED] wrote: 2/5 The previous patch fixed the last 2 places that directly access a runqueue's sched-domain and assume it cannot be NULL. We can now use a NULL domain instead of a dummy domain to signify no balancing is to happen. No functional changes.