From: Vegard Nossum <vegard.nossum@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] x86: fix incomplete include guard
Date: Tue, 27 May 2008 21:03:46 +0200 [thread overview]
Message-ID: <20080527190346.GA16422@damson.getinternet.no> (raw)
Hi,
It seems that suspend_32.h and xor_32.h are missing include guards too,
but I'm not touching those since I don't know if that's intended or not
:-)
Vegard
From: Vegard Nossum <vegard.nossum@gmail.com>
Date: Tue, 27 May 2008 20:50:42 +0200
Subject: [PATCH] x86: fix incomplete include guard
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
---
include/asm-x86/seccomp_32.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/asm-x86/seccomp_32.h b/include/asm-x86/seccomp_32.h
index 18da19e..36e71c5 100644
--- a/include/asm-x86/seccomp_32.h
+++ b/include/asm-x86/seccomp_32.h
@@ -1,4 +1,5 @@
#ifndef _ASM_SECCOMP_H
+#define _ASM_SECCOMP_H
#include <linux/thread_info.h>
--
1.5.4.1
next reply other threads:[~2008-05-27 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 19:03 Vegard Nossum [this message]
2008-06-02 10:47 ` [PATCH] x86: fix incomplete include guard Ingo Molnar
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=20080527190346.GA16422@damson.getinternet.no \
--to=vegard.nossum@gmail.com \
--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