From: "Steve French" <smfrench@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: lkml <linux-kernel@vger.kernel.org>,
"David Miller" <davem@davemloft.net>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: 2.6.26-pre build errors
Date: Fri, 25 Apr 2008 18:09:35 -0500 [thread overview]
Message-ID: <524f69650804251609j1b1d1161w18999f4692f130d1@mail.gmail.com> (raw)
In-Reply-To: <200804260042.32391.rjw@sisk.pl>
As expected, this patch resolved the link error.
On Fri, Apr 25, 2008 at 5:42 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Saturday, 26 of April 2008, Steve French wrote:
> > From today's current 2.6. kernel git tree - build included compile
> > errors in joystick support. After disabling joystick support, I still
> > get at least one link error:
> >
> > ERROR: "__locks_copy_lock" [fs/lockd/lockd.ko] undefined!
>
> Please try this:
>
> __locks_copy_lock has to be exported, because it's used in lockd,
> which may be built as a module.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> fs/locks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> Index: linux-2.6/fs/locks.c
> ===================================================================
> --- linux-2.6.orig/fs/locks.c
> +++ linux-2.6/fs/locks.c
> @@ -237,6 +237,8 @@ void __locks_copy_lock(struct file_lock
> new->fl_lmops = NULL;
> }
>
> +EXPORT_SYMBOL(__locks_copy_lock);
> +
> void locks_copy_lock(struct file_lock *new, struct file_lock *fl)
> {
> locks_release_private(new);
>
>
--
Thanks,
Steve
prev parent reply other threads:[~2008-04-25 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 22:33 Steve French
2008-04-25 22:42 ` Rafael J. Wysocki
2008-04-25 23:09 ` Steve French [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=524f69650804251609j1b1d1161w18999f4692f130d1@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®