From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Jes Sorensen <jes@sgi.com>,
Jack Steiner <steiner@sgi.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: bad patch in sched.c
Date: Sun, 11 Jan 2009 01:04:35 +0100 [thread overview]
Message-ID: <20090111000435.GF20843@elte.hu> (raw)
In-Reply-To: <4968D79C.10602@sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> Ingo Molnar wrote:
> > * Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> >> cpumask: fix CONFIG_NUMA=y sched.c
> >
> > doesnt build:
> >
> > kernel/sched.c: In function ‘__build_sched_domains’:
> > kernel/sched.c:7701: error: ‘struct static_sched_domain’ has no member named ‘sg’
> >
> > Ingo
> Hi,
>
> This one does compile and fix it.
applied to tip/sched/urgent, thanks Mike!
Ingo
prev parent reply other threads:[~2009-01-11 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 18:30 bad patch in sched.c Mike Travis
2009-01-10 12:04 ` Rusty Russell
2009-01-10 12:18 ` Ingo Molnar
2009-01-10 17:15 ` Mike Travis
2009-01-11 0:04 ` 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=20090111000435.GF20843@elte.hu \
--to=mingo@elte.hu \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.com \
--cc=travis@sgi.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