From: Paul Jackson <pj@sgi.com>
To: dino@in.ibm.com
Cc: paulus@samba.org, akpm@osdl.org, nickpiggin@yahoo.com.au,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@osdl.org, mingo@elte.hu, hawkes@sgi.com
Subject: Re: [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
Date: Wed, 24 Aug 2005 04:46:48 -0700 [thread overview]
Message-ID: <20050824044648.66f7e25a.pj@sgi.com> (raw)
In-Reply-To: <20050824112640.GB5197@in.ibm.com>
Dinakar wrote:
> Can we hold on to this patch for a while, as I reported yesterday,
Sure - though I guess it's Linus or Andrew who will have to do
the holding.
I sent it off contingent on the approval of yourself, Hawkes and Nick.
It looks like Linus is living dangerously and put it in already without
your approval. Hawkes reports of the oops if we didn't do something was
definitely motivating us to try something.
Good luck with your fix. Let us know when you understand it.
I'm not quite sure how close Linus is to releasing 2.6.13, or
what would best serve his needs here. The best I can do is push
on, be transparent, and let Linus holler if he has a better idea.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-08-24 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 11:15 [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix Paul Jackson
2005-08-24 11:26 ` Dinakar Guniguntala
2005-08-24 11:46 ` Paul Jackson [this message]
2005-08-24 12:01 ` Nick Piggin
2005-08-24 20:31 ` Paul Jackson
2005-08-25 0:02 ` Nick Piggin
2005-08-25 0:57 ` Paul Jackson
2005-08-25 14:41 ` Dinakar Guniguntala
2005-08-25 15:20 ` Paul Jackson
2005-08-24 16:09 ` John Hawkes
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=20050824044648.66f7e25a.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=hawkes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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