From: Arnd Bergmann <arnd@arndb.de>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
uClinux list <uclinux-dev@uclinux.org>
Subject: Re: [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table
Date: Tue, 19 Apr 2011 10:52:24 +0200 [thread overview]
Message-ID: <201104191052.24878.arnd@arndb.de> (raw)
In-Reply-To: <201104191021.20293.arnd@arndb.de>
On Tuesday 19 April 2011, Arnd Bergmann wrote:
> They are already sys_ni_syscall, by means of kernel/sys_ni.c.
> I wouldn't bother changing them. The real question is whether
> you should define the __NR_* macros for the syscalls that are
> not provided. For a new architecture I think you should not,
> but removing them might cause regressions. Then again, it's
> probably very useful to match the unistd.h file with the system
> call table.
I've just looked at the diff between the m68k and m68knommu
syscall tables, and it seems that you should be able to just
use the m68k variant, with a slight adaptation for mmap2/mmap_pgoff.
You might want to use the same method as asm-generic, in order
to provide a way to better synchronize unistd.h and syscalltable.
Arnd
next prev parent reply other threads:[~2011-04-19 8:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 20:33 [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table Geert Uytterhoeven
2011-04-06 22:05 ` [uClinux-dev] " Philippe De Muyter
[not found] ` <20110406220510.GA17350@frolo.macqel>
2011-04-07 0:53 ` Greg Ungerer
2011-04-07 2:12 ` Gavin Lambert
[not found] ` <000301cbf4c9$40339fc0$c09adf40$@com>
2011-04-07 2:43 ` Greg Ungerer
2011-04-07 3:13 ` Gavin Lambert
2011-04-07 4:14 ` Greg Ungerer
[not found] ` <4D9D3A28.9060104@snapgear.com>
2011-04-07 7:04 ` Geert Uytterhoeven
2011-04-07 8:29 ` Andreas Schwab
2011-04-07 8:35 ` Philippe De Muyter
2011-04-07 8:39 ` Andreas Schwab
2011-04-13 18:03 ` Geert Uytterhoeven
2011-04-07 1:53 ` Greg Ungerer
2011-04-13 18:16 ` Geert Uytterhoeven
2011-04-17 20:13 ` Arnd Bergmann
2011-04-19 4:32 ` Greg Ungerer
2011-04-19 8:21 ` Arnd Bergmann
2011-04-19 8:30 ` Geert Uytterhoeven
2011-04-19 8:52 ` Arnd Bergmann [this message]
2011-04-19 12:26 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2011-05-04 18:37 Geert Uytterhoeven
2011-05-04 22:18 ` Greg Ungerer
2011-05-05 6:24 ` Arnd Bergmann
2011-05-05 7:55 ` Greg Ungerer
2011-05-05 18:44 ` Geert Uytterhoeven
2011-05-05 20:37 ` Arnd Bergmann
2011-05-06 5:11 ` Geert Uytterhoeven
[not found] ` <BANLkTinqouGVWH8CmfM038TKFvhpJEczUQ@mail.gmail.com>
2011-05-06 8:24 ` Andreas Schwab
2011-05-06 18:56 ` Geert Uytterhoeven
2011-05-05 20:39 ` Mikael Pettersson
2011-05-07 8:34 ` Geert Uytterhoeven
2011-05-07 13:16 ` Mikael Pettersson
2011-10-23 9:53 ` Andreas Schwab
2011-10-23 12:20 ` Geert Uytterhoeven
2011-10-23 14:59 ` Andreas Schwab
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=201104191052.24878.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=uclinux-dev@uclinux.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