From: Greg Banks <gnb@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, neilb@suse.de, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1 of 4] cpumask: add highest_possible_node_id
Date: Mon, 16 Oct 2006 21:10:51 +1000 [thread overview]
Message-ID: <20061016111051.GH8568@sgi.com> (raw)
In-Reply-To: <20061016035644.1c99ad9b.pj@sgi.com>
On Mon, Oct 16, 2006 at 03:56:44AM -0700, Paul Jackson wrote:
> This patch (of August 3, 2006) added (after a bit of fixing) a nodemask
> related routine to lib/cpumask.c. Granted, there is no lib/nodemask.c,
> and Andrew suggested lib/cpumask.c.
>
> But at least it should have added
>
> #include <linux/nodemask.h>
>
> to lib/cpumask.c, no?
Sure.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
prev parent reply other threads:[~2006-10-16 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 5:35 [PATCH 1 of 4] cpumask: add highest_possible_node_id Greg Banks
2006-10-16 10:56 ` Paul Jackson
2006-10-16 11:10 ` Greg Banks [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=20061016111051.GH8568@sgi.com \
--to=gnb@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=pj@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