From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755288Ab1EPM6x (ORCPT ); Mon, 16 May 2011 08:58:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:25391 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755036Ab1EPM6u (ORCPT ); Mon, 16 May 2011 08:58:50 -0400 Date: Mon, 16 May 2011 14:57:03 +0200 From: Oleg Nesterov To: Mike Frysinger Cc: Linus Torvalds , Andrew Morton , Tejun Heo , "Nikita V. Youshchenko" , Matt Fleming , linux-kernel@vger.kernel.org Subject: Re: [PATCH] signal: trivial, fix the "timespec declared inside parameter list" warning Message-ID: <20110516125702.GA7941@redhat.com> References: <20110418134421.GA15951@redhat.com> <20110418173224.GA27918@redhat.com> <20110423175901.GA484@redhat.com> <20110426194822.GA8520@redhat.com> <20110426194904.GC8520@redhat.com> <20110513164435.GA22435@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/13, Mike Frysinger wrote: > > On Fri, May 13, 2011 at 12:44, Oleg Nesterov wrote: > > --- sigprocmask/include/linux/signal.h~15_stw_warning   2011-05-12 20:44:43.000000000 +0200 > > +++ sigprocmask/include/linux/signal.h  2011-05-13 18:10:40.000000000 +0200 > > @@ -242,6 +242,7 @@ extern int __group_send_sig_info(int, st > >  extern long do_rt_tgsigqueueinfo(pid_t tgid, pid_t pid, int sig, > >                                 siginfo_t *info); > >  extern long do_sigpending(void __user *, unsigned long); > > +struct timespec; > >  extern int do_sigtimedwait(const sigset_t *, siginfo_t *, > >                                const struct timespec *); > >  extern int sigprocmask(int, sigset_t *, sigset_t *); > > seems like you'd want to stick this higher up in the file (like after > the includes or at the top of the prototype block) OK, lets move it at the top of the prototype block. I'd like to keep it close to the user. If we do this, then we should probably move pt_regs as well. Oleg.