From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc64: Export flush_ptrace_access() (needed by lustre)
Date: Fri, 06 Sep 2013 12:56:13 +0000 [thread overview]
Message-ID: <20130906125613.GA6396@infradead.org> (raw)
In-Reply-To: <1378372110-19094-1-git-send-email-geert@linux-m68k.org>
On Thu, Sep 05, 2013 at 11:08:29AM +0200, Geert Uytterhoeven wrote:
> ERROR: "flush_ptrace_access" [drivers/staging/lustre/lustre/libcfs/libcfs.ko]
> undefined!
This seems to be more copy_to_user_page fallout, so instead of all these
arch patches we should figure out why lustre absolutely wants to use
this API that so far has been for core MM code only.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc64: Export flush_ptrace_access() (needed by lustre)
Date: Fri, 6 Sep 2013 05:56:13 -0700 [thread overview]
Message-ID: <20130906125613.GA6396@infradead.org> (raw)
In-Reply-To: <1378372110-19094-1-git-send-email-geert@linux-m68k.org>
On Thu, Sep 05, 2013 at 11:08:29AM +0200, Geert Uytterhoeven wrote:
> ERROR: "flush_ptrace_access" [drivers/staging/lustre/lustre/libcfs/libcfs.ko]
> undefined!
This seems to be more copy_to_user_page fallout, so instead of all these
arch patches we should figure out why lustre absolutely wants to use
this API that so far has been for core MM code only.
next prev parent reply other threads:[~2013-09-06 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 9:08 [PATCH] sparc64: Export flush_ptrace_access() (needed by lustre) Geert Uytterhoeven
2013-09-05 9:08 ` Geert Uytterhoeven
2013-09-06 12:56 ` Christoph Hellwig [this message]
2013-09-06 12:56 ` Christoph Hellwig
2013-09-06 12:58 ` Christoph Hellwig
2013-09-06 12:58 ` Christoph Hellwig
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=20130906125613.GA6396@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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 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.