public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Greg Banks <gnb@melbourne.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 03:56:44 -0700	[thread overview]
Message-ID: <20061016035644.1c99ad9b.pj@sgi.com> (raw)
In-Reply-To: <1154669719.21040.2351.camel@hole.melbourne.sgi.com>

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?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2006-10-16 10:57 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 [this message]
2006-10-16 11:10   ` Greg Banks

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=20061016035644.1c99ad9b.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=gnb@melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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