From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH -mmotm/fold] UV: fix header struct usage
Date: Sat, 31 Jan 2009 12:32:26 -0800 [thread overview]
Message-ID: <4984B55A.7060503@oracle.com> (raw)
In-Reply-To: <200901310909.n0V99XIZ021497@imap1.linux-foundation.org>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix uv.h struct usage:
arch/x86/include/asm/uv/uv.h:16: warning: 'struct mm_struct' declared inside parameter list
arch/x86/include/asm/uv/uv.h:16: warning: its scope is only this definition or declaration, which is probably not what you want
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
arch/x86/include/asm/uv/uv.h | 3 +++
1 file changed, 3 insertions(+)
--- mmotm-2009-0131-0108.orig/arch/x86/include/asm/uv/uv.h
+++ mmotm-2009-0131-0108/arch/x86/include/asm/uv/uv.h
@@ -3,6 +3,9 @@
enum uv_system_type {UV_NONE, UV_LEGACY_APIC, UV_X2APIC, UV_NON_UNIQUE_APIC};
+struct cpumask;
+struct mm_struct;
+
#ifdef CONFIG_X86_UV
extern enum uv_system_type get_uv_system_type(void);
prev parent reply other threads:[~2009-01-31 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901310909.n0V99XIZ021497@imap1.linux-foundation.org>
2009-01-31 19:53 ` mmotm 2009-01-31-01-08 uploaded (staging vs. mach64: CONFIG_PANEL) Randy Dunlap
2009-01-31 20:10 ` Andrew Morton
2009-02-02 23:00 ` [PATCH 1/2] atyfb: fix CONFIG_ namespace violations Randy Dunlap
2009-02-03 8:09 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2009-02-03 11:06 ` Ville Syrjälä
2009-02-03 22:23 ` Randy Dunlap
2009-02-03 23:58 ` Ville Syrjälä
2009-02-02 23:00 ` [PATCH 2/2] atyfb: fix header file trailing whitespace Randy Dunlap
2009-01-31 20:30 ` [PATCH -mmotm/fold] sysrq: emergency thaw only if CONFIG_BLOCK enabled Randy Dunlap
2009-01-31 20:32 ` Randy Dunlap [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=4984B55A.7060503@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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