From: Andrew Morton <akpm@digeo.com>
To: David Howells <dhowells@warthog.cambridge.redhat.com>
Cc: jgarzik@pobox.com, dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PAG support only
Date: Wed, 14 May 2003 03:00:31 -0700 [thread overview]
Message-ID: <20030514030031.13f7bf8f.akpm@digeo.com> (raw)
In-Reply-To: <18809.1052905491@warthog.warthog>
David Howells <dhowells@warthog.cambridge.redhat.com> wrote:
>
>
> So you'd rather have:
Doesn't matter.
We want all the code looking the same, and that is more important than the
arguable benefit of the minor changes which you propose.
> long sys_setpag(pag_t pag)
> {
> if (pag > 0) return vfs_join_pag(pag);
> else if (pag == 0) return vfs_leave_pag();
> else if (pag == -1) return vfs_new_pag();
> else return -EINVAL;
> }
If someone else comes along and makes changes to this, you'll end up with a
mix of styles.
> > and syscalls should return long, not int.
>
> Fair enough, but in arch/i386/kernel/process.c:
>
> asmlinkage int sys_fork(struct pt_regs regs)
> asmlinkage int sys_clone(struct pt_regs regs)
> asmlinkage int sys_vfork(struct pt_regs regs)
> asmlinkage int sys_execve(struct pt_regs regs)
> etc...
>
> Should these be fixed too (the i386 arch is referred to quite a lot)?
I don't know really. David M-T said "syscalls should return long". I'm
not sure why - perhaps it's only those which need 32-bit wrappers (guess).
next prev parent reply other threads:[~2003-05-14 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030513175240.6313ea92.akpm@digeo.com>
2003-05-14 9:44 ` David Howells
2003-05-14 10:00 ` Andrew Morton [this message]
2003-05-14 10:01 ` Miles Bader
2003-05-14 16:04 Chuck Ebbert
2003-05-14 16:20 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 16:33 David Howells
2003-05-13 16:48 ` Jeff Garzik
2003-05-13 20:37 ` Christoph Hellwig
2003-05-14 8:17 ` David Howells
2003-05-14 8:39 ` Christoph Hellwig
2003-05-14 4:57 ` Muli Ben-Yehuda
2003-05-14 9:54 ` David Howells
2003-05-14 12:35 ` Muli Ben-Yehuda
2003-05-14 13:17 ` David Howells
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=20030514030031.13f7bf8f.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=dhowells@redhat.com \
--cc=dhowells@warthog.cambridge.redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome