From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: [PATCH] Allow mpage.c to build
Date: Wed, 5 Jun 2002 16:05:47 +0100 [thread overview]
Message-ID: <20020605160547.C10293@flint.arm.linux.org.uk> (raw)
Linus,
When trying to build mpage.c for ARM, I get errors from bio.h since kdev_t
isn't defined. The following fixes this.
(I fail to see how this can build for anyone as it currently stands; its
probably something x86 specific buried in the asm-i386 includes.)
--- orig/fs/mpage.c Wed May 29 23:57:08 2002
+++ linux/fs/mpage.c Thu May 30 00:34:44 2002
@@ -12,6 +12,7 @@
#include <linux/kernel.h>
#include <linux/module.h>
+#include <linux/kdev_t.h>
#include <linux/bio.h>
#include <linux/fs.h>
#include <linux/buffer_head.h>
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2002-06-05 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 15:05 Russell King [this message]
2002-06-05 19:49 ` [PATCH] Allow mpage.c to build Andrew Morton
2002-06-05 19:59 ` Dave Jones
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=20020605160547.C10293@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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