[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVyT6R6mYnVuv9vqmeCC7_TB2KZPCqfcmMyLvjbZPs+Ag@mail.gmail.com>
Date: Sun, 8 May 2016 18:25:48 -0700
From: Andy Lutomirski <luto@...capital.net>
To: René Nyffenegger <mail@...enyffenegger.ch>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Josh Triplett <josh@...htriplett.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Steven Rostedt (Red Hat)" <rostedt@...dmis.org>,
Zach Brown <zab@...hat.com>, Milosz Tanski <milosz@...in.com>,
Arnd Bergmann <arnd@...db.de>,
Linux API <linux-api@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Use pid_t instead of int
On Sun, May 8, 2016 at 12:38 PM, René Nyffenegger
<mail@...enyffenegger.ch> wrote:
> Use pid_t instead of int in the declarations of sys_kill, sys_tgkill,
> sys_tkill and sys_rt_sigqueueinfo in include/linux/syscalls.h
The description is no good. *Why* are you changing it?
I checked tgkill and, indeed, tgkill takes pid_t parameters, so this
fixes an incorrect declaration. I'm wondering why the code compiles
without warning. Is SYSCALL_DEFINE too lenient for some reason? Or
is pid_t just defined as int.
--Andy
Powered by blists - more mailing lists