From: "Hyok S. Choi" <hyok.choi@samsung.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: MMUless CPU support?
Date: Fri, 14 May 2004 18:39:22 +0900 [thread overview]
Message-ID: <40A493CA.7030702@samsung.com> (raw)
In-Reply-To: <20040513174521.A10776@flint.arm.linux.org.uk>
Russell King - ARM Linux wrote:
>On Thu, May 13, 2004 at 06:17:09PM +0200, Vadim Lebedev wrote:
>
>
>>Hyok,
>>
>>about fork and mmap syscalls on uClinux:
>>
>>actually i believe it would be better to leave calls.S untouched and return
>>EINVAL or similar in the C level code...
>>BTW, if i remember correctly (it was in 97 when i've ported uClinux 2.0.xx
>>from 68000 to ARM7) mmap call was partially functionnal on ucLinux
>>(depending
>>on arguments) so
>> there is no need to scrap it from calls.S too....
>>
>>the less we touch .S file the eathier it'll be to maintain the NO-MMU
>>version
>>
>>
>
>And you can use assembler/linker magic to alias sys_fork to
>sys_ni_syscall.
>
>Since Hyok seems to be 100% against any kind of merge, it's useless
>even talking about this though.
>
>
Hmm, I think about the clean and well structured kind of merge. His
comment was useful for me. :-)
I always think almost all of tricky method to cross among codes is NO
good, for maintainer, code readers, porting guys and all.
I like Vadim's method.
Regards,
Hyok
next parent reply other threads:[~2004-05-14 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405040617.42342.jeffs@fairwayacademy.org>
[not found] ` <409AC200.7020106@mailcan.com>
[not found] ` <20040507084536.A14179@flint.arm.linux.org.uk>
[not found] ` <409B97E4.8010100@snapgear.com>
[not found] ` <20040507194740.A5778@flint.arm.linux.org.uk>
[not found] ` <409E3752.3050102@snapgear.com>
[not found] ` <20040509152414.C17714@flint.arm.linux.org.uk>
[not found] ` <409EC97D.7030105@samsung.com>
[not found] ` <20040510094435.B27722@flint.arm.linux.org.uk>
[not found] ` <409F62D5.6080500@samsung.com>
[not found] ` <20040510123124.C27722@flint.arm.linux.org.uk>
[not found] ` <409F7341.4090207@samsung.com>
[not found] ` <042601c43905$beed50e0$0100a8c0@SHUTTLE>
[not found] ` <20040513174521.A10776@flint.arm.linux.org.uk>
2004-05-14 9:39 ` Hyok S. Choi [this message]
2004-05-16 7:58 ` MMUless CPU support? Christoph Hellwig
2004-05-16 8:18 ` Russell King
2004-05-17 0:35 ` Hyok S. Choi
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=40A493CA.7030702@samsung.com \
--to=hyok.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.