From: travis@sgi.com
To: Andrew Morton <akpm@linux-foundation.org>,
Paul Jackson <pj@sgi.com>, Tony Luck <tony.luck@intel.com>,
Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mike Travis <travis@sgi.com>
Subject: [PATCH 0/1] ia64: Convert cpu_sibling_map to a per_cpu data array FIX
Date: Thu, 04 Oct 2007 15:31:41 -0700 [thread overview]
Message-ID: <20071004223141.413776000@sgi.com> (raw)
The previous version of this patch missed a code path in
inserting the boot cpu into the cpu sibling and core maps.
This fix corrects that omission.
--
--
WARNING: multiple messages have this Message-ID (diff)
From: travis@sgi.com
To: Andrew Morton <akpm@linux-foundation.org>,
Paul Jackson <pj@sgi.com>, Tony Luck <tony.luck@intel.com>,
Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mike Travis <travis@sgi.com>
Subject: [PATCH 0/1] ia64: Convert cpu_sibling_map to a per_cpu data array FIX
Date: Thu, 04 Oct 2007 15:31:41 -0700 [thread overview]
Message-ID: <20071004223141.413776000@sgi.com> (raw)
The previous version of this patch missed a code path in
inserting the boot cpu into the cpu sibling and core maps.
This fix corrects that omission.
--
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2007-10-04 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 22:31 travis [this message]
2007-10-04 22:31 ` [PATCH 0/1] ia64: Convert cpu_sibling_map to a per_cpu data array FIX travis
2007-10-04 22:31 ` [PATCH 1/1] " travis
2007-10-04 22:31 ` travis
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=20071004223141.413776000@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.