From: Juan Quintela <quintela@mandrakesoft.com>
To: paulus@samba.org
Cc: Benjamin LaHaise <bcrl@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [bkpatch] do_mmap cleanup
Date: 09 Mar 2002 22:17:22 +0100 [thread overview]
Message-ID: <m27kolmof1.fsf@trasno.mitica> (raw)
In-Reply-To: <15497.61055.615126.619184@argo.ozlabs.ibm.com>
>>>>> "paul" == Paul Mackerras <paulus@samba.org> writes:
paul> Juan Quintela writes:
>> Please, don't do that, export another function that does exactly that.
>> sys_munmap is declared as asmlinkage, and some architectures (at
>> least ppc used to have) need especial code to be able to call
>> asmlinkage functions from inside the kernel.
paul> Huh? asmlinkage doesn't do anything on PPC, and never has. It only
paul> makes any difference on i386 and ia64 - see include/linux/linkage.h.
Humm, having to relook at the question. When I begin to work in
supermount, there was a need for a patch (trampoline.S), that I don't
need anymore after I remove one asmlinkage from the exported
functions. But if you told that it is not needed, you are the ppc
maintainer, can be that any side effect made that code not to be
needed anymore.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-03-09 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 23:53 Benjamin LaHaise
2002-03-09 2:15 ` Juan Quintela
2002-03-09 11:14 ` Paul Mackerras
2002-03-09 21:17 ` Juan Quintela [this message]
2002-03-11 12:08 ` Pavel Machek
2002-03-11 19:18 ` Benjamin LaHaise
2002-03-11 20:39 ` Tom Rini
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=m27kolmof1.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulus@samba.org \
--cc=torvalds@transmeta.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