Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Masahiro Yamada
On Sun, Feb 3, 2019 at 1:33 AM Alexey Dobriyan wrote: > > On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > > and others") did not explain why it used (s16) and (u16) instead of > > (short) and (unsigned short

Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Alexey Dobriyan
On Sat, Feb 02, 2019 at 07:31:05PM +0300, Alexey Dobriyan wrote: > On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > > and others") did not explain why it used (s16) and (u16) instead of > > (short) and (unsign

Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Alexey Dobriyan
On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > and others") did not explain why it used (s16) and (u16) instead of > (short) and (unsigned short). > > Let's use (short) and (unsigned short), which is more sen

[PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Masahiro Yamada
The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX and others") did not explain why it used (s16) and (u16) instead of (short) and (unsigned short). Let's use (short) and (unsigned short), which is more sensible, and more consistent with the other MAX/MIN defines. As you see in i