public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Dean Roe <roe@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix for-loop in sn_hwperf_geoid_to_cnode()
Date: Wed, 08 Mar 2006 22:02:06 +0000	[thread overview]
Message-ID: <20060308220206.GA11094@sgi.com> (raw)
In-Reply-To: <20060303150312.GA32225@sgi.com>

On Mon, Mar 06, 2006 at 10:35:19AM -0700, Bjorn Helgaas wrote:
> On Monday 06 March 2006 09:32, Dean Roe wrote:
> > -	for_each_node(cnode) {
> > +	/*
> > +	 * FIXME: replace with cleaner for_each_XXX macro which addresses
> > +	 * both compute and IO nodes once ACPI3.0 is available.
> > +	 */
> > +	for (cnode = 0; cnode < num_cnodes; cnode++) {
> 
> I don't understand this ACPI 3.0 dependency.  Can't you just define
> for_each_XXX() the way you want it, and fill in the bitmask or whatever
> it uses either (a) using ACPI 3.0 data, or (b) some interim hack?
> 
> Bjorn

I can't really tell from your response, so...did you see Jack's explanation
of this?
    http://marc.theaimsgroup.com/?l=linux-ia64&m\x114141537904761&w=2

Are you saying you *really* want a for_each_sn_cnode() macro?  I guess
we can go that route if necessary...I just prefer the one-line change
rather than changing 4-5 files when we aren't really sure yet what the
final implementation will look like.  I just want to make sure I am reading
you correctly.

Thanks,
Dean

-- 
Dean Roe
Silicon Graphics, Inc.
roe@sgi.com

  parent reply	other threads:[~2006-03-08 22:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 15:03 [PATCH] fix for-loop in sn_hwperf_geoid_to_cnode() Dean Roe
2006-03-03 17:01 ` Luck, Tony
2006-03-03 19:49 ` Jack Steiner
2006-03-03 21:52 ` Luck, Tony
2006-03-06 16:28 ` Dean Roe
2006-03-06 16:32 ` Dean Roe
2006-03-06 17:35 ` Bjorn Helgaas
2006-03-08 22:02 ` Dean Roe [this message]
2006-03-08 23:55 ` Bjorn Helgaas
2006-03-09 16:12 ` Robin Holt
2006-03-09 17:57 ` Bjorn Helgaas
2006-03-10 17:57 ` Jack Steiner

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=20060308220206.GA11094@sgi.com \
    --to=roe@sgi.com \
    --cc=linux-ia64@vger.kernel.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