From: Robert Love <rml@tech9.net>
To: John Weber <weber@nyc.rr.com>, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Re: 2.5.3 Link Error
Date: 30 Jan 2002 17:18:46 -0500 [thread overview]
Message-ID: <1012429142.3392.79.camel@phantasy> (raw)
In-Reply-To: <3C586D98.5090900@nyc.rr.com>
In-Reply-To: <3C586D98.5090900@nyc.rr.com>
iOn Wed, 2002-01-30 at 17:03, John Weber wrote:
> -o vmlinux
> fs/fs.o: In function `cap_info_llseek':
> fs/fs.o(.text+0x4e1d1): undefined reference to `lock_kernel'
> fs/fs.o(.text+0x4e220): undefined reference to `unlock_kernel'
> fs/fs.o: In function `hdr_llseek':
> fs/fs.o(.text+0x4e858): undefined reference to `lock_kernel'
> fs/fs.o(.text+0x4e8b6): undefined reference to `unlock_kernel'
> make: *** [vmlinux] Error 1
Whoops, missed that in the BKL removal patch. This should fix it.
Linus, please apply.
Robert Love
diff -urN linux-2.5.3/fs/hfs/file_cap.c linux/fs/hfs/file_cap.c
--- linux-2.5.3/fs/hfs/file_cap.c Wed Jan 30 16:12:03 2002
+++ linux/fs/hfs/file_cap.c Wed Jan 30 17:08:09 2002
@@ -24,6 +24,7 @@
#include <linux/hfs_fs_sb.h>
#include <linux/hfs_fs_i.h>
#include <linux/hfs_fs.h>
+#include <linux/smp_lock.h>
/*================ Forward declarations ================*/
static loff_t cap_info_llseek(struct file *, loff_t,
diff -urN linux-2.5.3/fs/hfs/file_hdr.c linux/fs/hfs/file_hdr.c
--- linux-2.5.3/fs/hfs/file_hdr.c Wed Jan 30 16:12:03 2002
+++ linux/fs/hfs/file_hdr.c Wed Jan 30 17:10:31 2002
@@ -29,6 +29,7 @@
#include <linux/hfs_fs_sb.h>
#include <linux/hfs_fs_i.h>
#include <linux/hfs_fs.h>
+#include <linux/smp_lock.h>
/* prodos types */
#define PRODOSI_FTYPE_DIR 0x0F
prev parent reply other threads:[~2002-01-30 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 22:03 2.5.3 Link Error John Weber
2002-01-30 22:18 ` Robert Love [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=1012429142.3392.79.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=weber@nyc.rr.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