From: Bernd Schmidt <bernds_cb1@t-online.de>
To: bryan.wu@analog.com
Cc: Mike Frysinger <vapier.adi@gmail.com>,
bernd.schmidt@analog.com, linux-arch@vger.kernel.org,
Matthew Wilcox <matthew@wil.cx>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Paul Mundt <lethal@linux-sh.org>,
uclinux-dist-devel@blackfin.uclinux.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Uclinux-dist-devel] Re: [PATCH] Blackfin arch: add some missing syscall
Date: Thu, 13 Sep 2007 13:03:25 +0200 [thread overview]
Message-ID: <46E918FD.3070607@t-online.de> (raw)
In-Reply-To: <1189673849.30686.28.camel@roc-desktop>
Bryan Wu wrote:
>>> but mremap doesn't -- there's even an implementation in mm/nommu.c.
>>> Could you check the rest of these over to see if they truly don't need
>>> to be implemented for no-mmu?
>> you're right we want mremap, my fault
>>
>
> Yes, I do think so, both sys_mremap and sys_munmap are implemented in
> mm/nommu.c. How do think of this, Bernd?
There's a mremap in nommu.c, but it doesn't do a lot that is useful.
With some further mm changes in our tree, it's little more than a fancy
way of saying munmap, and uClibc does not use it, so there's no
compelling need to have it in userspace.
Bernd
--
This footer brought to you by insane German lawmakers.
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 40368
Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
next prev parent reply other threads:[~2007-09-13 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 7:56 [PATCH] Blackfin arch: add some missing syscall Bryan Wu
2007-09-13 8:07 ` Paul Mundt
2007-09-13 8:09 ` Paul Mundt
2007-09-13 8:18 ` Matthew Wilcox
2007-09-13 8:37 ` Mike Frysinger
2007-09-13 8:57 ` Bryan Wu
2007-09-13 11:03 ` Bernd Schmidt [this message]
2007-09-14 5:45 ` [Uclinux-dist-devel] " Bryan Wu
2007-09-14 6:44 ` Mike Frysinger
2007-09-14 7:32 ` Bryan Wu
2007-09-15 1:28 ` Mike Frysinger
2007-09-13 8:47 ` 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=46E918FD.3070607@t-online.de \
--to=bernds_cb1@t-online.de \
--cc=akpm@linux-foundation.org \
--cc=bernd.schmidt@analog.com \
--cc=bryan.wu@analog.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@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;
as well as URLs for NNTP newsgroup(s).