From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6 patch] kernel/sys_ni.c should #include <linux/syscalls.h>
Date: Mon, 18 Jun 2007 01:43:01 +0200 [thread overview]
Message-ID: <20070617234301.GF3588@stusta.de> (raw)
Every file should include the headers containing the prototypes for
it's global functions.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
--- linux-2.6.22-rc4-mm2/kernel/sys_ni.c.old 2007-06-17 16:03:11.000000000 +0200
+++ linux-2.6.22-rc4-mm2/kernel/sys_ni.c 2007-06-17 16:03:30.000000000 +0200
@@ -1,6 +1,7 @@
#include <linux/linkage.h>
#include <linux/errno.h>
+#include <linux/syscalls.h>
#include <asm/unistd.h>
reply other threads:[~2007-06-17 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070617234301.GF3588@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@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
Powered by JetHome