From: Matthew Dobson <colpatch@us.ibm.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jesse Barnes <jbarnes@sgi.com>, Andi Kleen <ak@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
LSE Tech <lse-tech@lists.sourceforge.net>
Subject: Re: [Lse-tech] [RFC][PATCH] Change pcibus_to_cpumask() to pcibus_to_node()
Date: Fri, 30 Jul 2004 15:33:19 -0700 [thread overview]
Message-ID: <1091226799.5925.4.camel@arrakis> (raw)
In-Reply-To: <200407301521.03422.jbarnes@engr.sgi.com>
On Fri, 2004-07-30 at 15:21, Jesse Barnes wrote:
> On Friday, July 30, 2004 3:17 pm, Matthew Dobson wrote:
> > On Fri, 2004-07-30 at 08:36, Jesse Barnes wrote:
> > > I think this will work. My tree didn't have nodemask_t though, so it
> > > didn't compile :) Here's a first stab at an ia64 portion of the patch.
> > >
> > > Jesse
> >
> > Andrew picked it up in 2.6.8-rc2-mm1, so if you base your patch against
> > that it should compile... That's what I based my patch off. Our lab
> > has been down for a few days so I hope to do some testing on Monday for
> > my patches. If all goes well, I'll add your code into my patch and
> > submit it early next week, ok?
>
> Sounds good, but it will probably need some fixes before it works correctly
> (my stuff I mean), so when you have something that looks good give me a few
> minutes with it before you send it on to Andrew if you would.
>
> Thanks,
> Jesse
No problem, Jesse. Like I said, with lab machines being decidedly
unfriendly, I won't even be able to run any real tests on my code until
Monday at the earliest. I'll certainly give you at least 5 minutes
warning before I post any untested, potentially dangerous code! ;)
-Matt
next prev parent reply other threads:[~2004-07-30 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 0:10 [RFC][PATCH] Change pcibus_to_cpumask() to pcibus_to_node() Matthew Dobson
2004-07-27 3:38 ` Jesse Barnes
2004-07-27 9:51 ` [Lse-tech] " Christoph Hellwig
2004-07-27 15:22 ` Jesse Barnes
2004-07-27 18:32 ` Matthew Dobson
2004-07-27 18:40 ` Jesse Barnes
2004-07-29 0:06 ` Matthew Dobson
2004-07-29 15:43 ` Jesse Barnes
2004-07-29 22:23 ` Matthew Dobson
2004-07-30 15:36 ` Jesse Barnes
2004-07-30 22:17 ` Matthew Dobson
2004-07-30 22:21 ` Jesse Barnes
2004-07-30 22:33 ` Matthew Dobson [this message]
2004-07-29 17:02 ` Rajesh Shah
2004-07-29 22:27 ` Matthew Dobson
2004-07-30 0:02 ` Rajesh Shah
2004-07-28 15:01 ` Martin J. Bligh
2004-07-28 19:10 ` Matthew Dobson
2004-07-27 14:16 ` Andi Kleen
2004-07-27 15:15 ` Jesse Barnes
2004-07-27 15:57 ` Andi Kleen
2004-07-27 18:18 ` Matthew Dobson
2004-07-29 8:34 ` Paul Jackson
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=1091226799.5925.4.camel@arrakis \
--to=colpatch@us.ibm.com \
--cc=ak@suse.de \
--cc=hch@infradead.org \
--cc=jbarnes@engr.sgi.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.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