From: Jeff Dike <jdike@addtoit.com>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
WANG Cong <xiyou.wangcong@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>
Subject: Re: [uml-devel] [-mm Patch] uml: fix a building error
Date: Thu, 17 Jan 2008 13:56:25 -0500 [thread overview]
Message-ID: <20080117185625.GA5724@c2.user-mode-linux.org> (raw)
In-Reply-To: <200801171911.16230.m.kozlowski@tuxland.pl>
On Thu, Jan 17, 2008 at 07:11:13PM +0100, Mariusz Kozlowski wrote:
> I see this on sparc64 as well:
>
> CC drivers/char/mem.o
> drivers/char/mem.c: In function 'read_mem':
> drivers/char/mem.c:136: error: implicit declaration of function 'unxlate_dev_mem_ptr'
> make[2]: *** [drivers/char/mem.o] Error 1
> make[1]: *** [drivers/char] Error 2
> make: *** [drivers] Error 2
>
> Does sparc64 need similar fix?
Probably - it seems that xlate_dev_mem_ptr can now introduce
side-effects which need to be undone with unxlate_dev_mem_ptr.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2008-01-17 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080117023514.9df393cf.akpm@linux-foundation.org>
2008-01-17 13:21 ` [uml-devel] [-mm Patch] UML: fix a building error WANG Cong
2008-01-17 17:59 ` Jeff Dike
2008-01-17 13:56 ` [uml-devel] [-mm Patch] uml: " WANG Cong
2008-01-17 17:59 ` Jeff Dike
2008-01-17 18:11 ` Mariusz Kozlowski
2008-01-17 18:56 ` Andrew Morton
2008-01-17 19:38 ` Pallipadi, Venkatesh
2008-01-17 19:44 ` Andrew Morton
2008-01-17 20:42 ` Mariusz Kozlowski
2008-01-17 21:14 ` Jeff Dike
2008-01-17 21:41 ` Venki Pallipadi
2008-01-17 23:08 ` Jeff Dike
2008-01-17 23:17 ` Pallipadi, Venkatesh
2008-01-18 2:19 ` Jeff Dike
2008-01-17 18:56 ` Jeff Dike [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=20080117185625.GA5724@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=sparclinux@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=xiyou.wangcong@gmail.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