Arnd Bergmann writes:
> On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
>> Arnd Bergmann writes:
>> > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
>> > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 +++
>> > arch/powerpc/kernel/syscalls/syscall.tbl | 12
Arnd Bergmann writes:
> On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
>>
>> On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
>> > Arnd Bergmann writes:
>> > > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
>> > > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 ++
On Tue, Jan 15, 2019 at 5:36 PM Geert Uytterhoeven wrote:
> On Tue, Jan 15, 2019 at 4:19 PM Arnd Bergmann wrote:
> > On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
> > > On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman
> > > wrote:
> > > > Arnd Bergmann writes:
> > > > > arch/m68k/kern
Hi Arnd,
On Tue, Jan 15, 2019 at 4:19 PM Arnd Bergmann wrote:
> On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
> > On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman
> > wrote:
> > > Arnd Bergmann writes:
> > > > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
> > > > arch/mi
On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
>
> On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
> > Arnd Bergmann writes:
> > > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
> > > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 +++
> > > arch/powerpc/kerne
On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
> Arnd Bergmann writes:
> > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
> > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 +++
> > arch/powerpc/kernel/syscalls/syscall.tbl | 12
>
> I have some changes
Michael Ellerman writes:
> Hi Arnd,
>
> Arnd Bergmann writes:
>> The IPC system call handling is highly inconsistent across architectures,
>> some use sys_ipc, some use separate calls, and some use both. We also
>> have some architectures that require passing IPC_64 in the flags, and
>> others t
Hi Arnd,
Arnd Bergmann writes:
> The IPC system call handling is highly inconsistent across architectures,
> some use sys_ipc, some use separate calls, and some use both. We also
> have some architectures that require passing IPC_64 in the flags, and
> others that set it implicitly.
>
> For the
Hi Arnd,
Arnd Bergmann writes:
> The IPC system call handling is highly inconsistent across architectures,
> some use sys_ipc, some use separate calls, and some use both. We also
> have some architectures that require passing IPC_64 in the flags, and
> others that set it implicitly.
>
> For the
On Thu, Jan 10, 2019 at 9:33 PM Heiko Carstens
wrote:
> On Thu, Jan 10, 2019 at 05:24:34PM +0100, Arnd Bergmann wrote:
> > diff --git a/arch/s390/kernel/syscalls/syscall.tbl
> > b/arch/s390/kernel/syscalls/syscall.tbl
> > index 022fc099b628..428cf512a757 100644
> > --- a/arch/s390/kernel/syscall
On Thu, Jan 10, 2019 at 05:24:34PM +0100, Arnd Bergmann wrote:
> The IPC system call handling is highly inconsistent across architectures,
> some use sys_ipc, some use separate calls, and some use both. We also
> have some architectures that require passing IPC_64 in the flags, and
> others that s
The IPC system call handling is highly inconsistent across architectures,
some use sys_ipc, some use separate calls, and some use both. We also
have some architectures that require passing IPC_64 in the flags, and
others that set it implicitly.
For the additon of a y2083 safe semtimedop() system
12 matches
Mail list logo