From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: viro@math.psu.edu, Rasmus Andersen <rasmus@jaquet.dk>,
linux-kernel@vger.kernel.org
Subject: PATCH 2.4.0.11.3: sysctl.h fixes
Date: Sun, 12 Nov 2000 09:30:59 -0500 [thread overview]
Message-ID: <200011121430.JAA22978@havoc.gtf.org> (raw)
Rasmus Andersen wrote:
> I tried to include <linux/types.h> in md.c and had to include
> <linux/blkdev.h> also. Otherwise I got the following:
Here is the solution I prefer... md builds fine with this, core kernel builds fine with this, and
I'm about 3/4 of the way through a "build everything" build with this.
I tried to avoid including fs.h, but I do prefer updating sysctl.h, because it fixes potential
breakage similar to md's as well.
Jeff
Index: include/linux/sysctl.h
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/include/linux/sysctl.h,v
retrieving revision 1.1.1.8
diff -u -r1.1.1.8 sysctl.h
--- include/linux/sysctl.h 2000/10/31 21:19:40 1.1.1.8
+++ include/linux/sysctl.h 2000/11/12 14:28:04
@@ -24,7 +24,11 @@
#ifndef _LINUX_SYSCTL_H
#define _LINUX_SYSCTL_H
+#include <linux/kernel.h>
+#include <linux/types.h>
#include <linux/list.h>
+
+struct file;
#define CTL_MAXNAME 10
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-12 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-12 14:30 Jeff Garzik [this message]
2000-11-12 23:02 ` PATCH 2.4.0.11.3: sysctl.h fixes Neil Brown
2000-11-12 23:28 ` Jeff Garzik
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=200011121430.JAA22978@havoc.gtf.org \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).