From: travis@sgi.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] fix possible undefined PER_CPU_ATTRIBUTES
Date: Tue, 22 Jan 2008 13:15:29 -0800 [thread overview]
Message-ID: <20080122211528.797776000@sgi.com> (raw)
In-Reply-To: 20080122211528.602673000@sgi.com
[-- Attachment #1: fix-PER_CPU_ATTRIBUTES-define --]
[-- Type: text/plain, Size: 599 bytes --]
Not sure how this leaked out and I haven't caught it yet in my
cross-build testing but to be on the safe side, PER_CPU_ATTRIBUTES
should be defined.
Applies to 2.6.24-rc8-mm1 + percpu changes
Signed-off-by: Mike Travis <travis@sgi.com>
---
include/linux/percpu.h | 4 ++++
1 file changed, 4 insertions(+)
--- a/include/linux/percpu.h
+++ b/include/linux/percpu.h
@@ -9,6 +9,10 @@
#include <asm/percpu.h>
+#ifndef PER_CPU_ATTRIBUTES
+#define PER_CPU_ATTRIBUTES
+#endif
+
#ifdef CONFIG_SMP
#define DEFINE_PER_CPU(type, name) \
__attribute__((__section__(".data.percpu"))) \
--
WARNING: multiple messages have this Message-ID (diff)
From: travis@sgi.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] fix possible undefined PER_CPU_ATTRIBUTES
Date: Tue, 22 Jan 2008 13:15:29 -0800 [thread overview]
Message-ID: <20080122211528.797776000@sgi.com> (raw)
In-Reply-To: 20080122211528.602673000@sgi.com
[-- Attachment #1: fix-PER_CPU_ATTRIBUTES-define --]
[-- Type: text/plain, Size: 825 bytes --]
Not sure how this leaked out and I haven't caught it yet in my
cross-build testing but to be on the safe side, PER_CPU_ATTRIBUTES
should be defined.
Applies to 2.6.24-rc8-mm1 + percpu changes
Signed-off-by: Mike Travis <travis@sgi.com>
---
include/linux/percpu.h | 4 ++++
1 file changed, 4 insertions(+)
--- a/include/linux/percpu.h
+++ b/include/linux/percpu.h
@@ -9,6 +9,10 @@
#include <asm/percpu.h>
+#ifndef PER_CPU_ATTRIBUTES
+#define PER_CPU_ATTRIBUTES
+#endif
+
#ifdef CONFIG_SMP
#define DEFINE_PER_CPU(type, name) \
__attribute__((__section__(".data.percpu"))) \
--
--
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 prev parent reply other threads:[~2008-01-22 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 21:15 [PATCH 0/1] dummy header travis
2008-01-22 21:15 ` travis [this message]
2008-01-22 21:15 ` [PATCH 1/1] fix possible undefined PER_CPU_ATTRIBUTES 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=20080122211528.797776000@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.