From: Paul Mundt <lethal@linux-sh.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: Build fix: define __movmem
Date: Wed, 30 Sep 2009 06:42:27 +0000 [thread overview]
Message-ID: <20090930064227.GA5967@linux-sh.org> (raw)
In-Reply-To: <1254291454-7436-1-git-send-email-lkundrak@v3.sk>
On Wed, Sep 30, 2009 at 08:17:34AM +0200, Lubomir Rintel wrote:
> ERROR: "__movmem" [net/irda/irda.ko] undefined!
> ERROR: "__movmem" [fs/nfsd/nfsd.ko] undefined!
> ERROR: "__movmem" [fs/lockd/lockd.ko] undefined!
> ERROR: "__movmem" [crypto/sha1_generic.ko] undefined!
> ---
> arch/sh/kernel/sh_ksyms_32.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: Build fix: define __movmem
Date: Wed, 30 Sep 2009 15:42:27 +0900 [thread overview]
Message-ID: <20090930064227.GA5967@linux-sh.org> (raw)
In-Reply-To: <1254291454-7436-1-git-send-email-lkundrak@v3.sk>
On Wed, Sep 30, 2009 at 08:17:34AM +0200, Lubomir Rintel wrote:
> ERROR: "__movmem" [net/irda/irda.ko] undefined!
> ERROR: "__movmem" [fs/nfsd/nfsd.ko] undefined!
> ERROR: "__movmem" [fs/lockd/lockd.ko] undefined!
> ERROR: "__movmem" [crypto/sha1_generic.ko] undefined!
> ---
> arch/sh/kernel/sh_ksyms_32.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
Applied, thanks.
next prev parent reply other threads:[~2009-09-30 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 6:17 [PATCH] sh: Build fix: define __movmem Lubomir Rintel
2009-09-30 6:17 ` Lubomir Rintel
2009-09-30 6:42 ` Paul Mundt [this message]
2009-09-30 6:42 ` Paul Mundt
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=20090930064227.GA5967@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkundrak@v3.sk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.