Thread (13 messages) 13 messages, 7 authors, 2015-09-16

Re: linux-next: manual merge of the akpm-current tree with the tip tree

From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2015-09-16 06:58:35
Also in: lkml

Hi Andrew,

On Wed, Sep 9, 2015 at 1:21 AM, Andrew Morton [off-list ref] wrote:
New syscalls are rather a pain, both from the patch-monkeying POV and
also because nobody knows what the syscall numbers will be until
everything lands in mainline.  Oh well, it doesn't happen often and
it's easy stuff.
One more reason to let the assignment of syscall numbers be handled
(1) by the architecture maintainer, (2) after -rc1, even for x86.

If x86 is no more the canonical source, scripts/checksyscalls.sh needs an
update, though.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help