[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdWnPx1HsySNhFSdDfVoSew81tnrVyoaWJezyfKMHc7zSw@mail.gmail.com>
Date: Sun, 20 Sep 2015 15:28:09 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Andreas Schwab <schwab@...ux-m68k.org>
Cc: Greg Ungerer <gerg@...inux.org>,
"Linux/m68k" <linux-m68k@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Andy Lutomirski <luto@...capital.net>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: Drop IPC_OLD for direct ipc syscalls?
Hi Andreas,
On Sun, Sep 20, 2015 at 12:38 PM, Andreas Schwab <schwab@...ux-m68k.org> wrote:
> Geert Uytterhoeven <geert@...ux-m68k.org> writes:
>
>> Should I postpone wiring up the direct ipc syscalls on m68k (and thus renumber
>> __NR_membarrier) until the above is resolved, or can they go in in v4.3?
>
> If you wire up the direct ipc calls know you create an ABI that is
> harder to get rid of.
That's what I was mostly worried about.
Thanks for confirming!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists