Subject: Re: [PATCH] headers_check fix: linux/pps.h
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
       Randy Dunlap <randy.dunlap@oracle.com>,
       Rodolfo Giometti <giometti@linux.it>,
       Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Michael Kerrisk <mtk.manpages@googlemail.com>,
       LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <1246166231.4497.5.camel@hpdv5.satnam>
References: <1246120414.32198.5.camel@hpdv5.satnam>
	 <20090627215346.GA2719@uranus.ravnborg.org>
	 <1246166231.4497.5.camel@hpdv5.satnam>
Content-Type: text/plain
Date: Sun, 28 Jun 2009 11:07:30 +0530
Message-Id: <1246167450.4497.14.camel@hpdv5.satnam>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2067
Lines: 60

On Sun, 2009-06-28 at 10:47 +0530, Jaswinder Singh Rajput wrote:
> On Sat, 2009-06-27 at 23:53 +0200, Sam Ravnborg wrote:
> > On Sat, Jun 27, 2009 at 10:03:34PM +0530, Jaswinder Singh Rajput wrote:
> > > 
> > > fix the following 'make headers_check' warnings:
> > > 
> > >   usr/include/linux/pps.h:52: found __[us]{8,16,32,64} type without #include <linux/types.h>
> > > 
> > > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > > ---
> > >  include/linux/pps.h |    2 ++
> > >  1 files changed, 2 insertions(+), 0 deletions(-)
> > > 
> > > diff --git a/include/linux/pps.h b/include/linux/pps.h
> > > index cfe5c72..0194ab0 100644
> > > --- a/include/linux/pps.h
> > > +++ b/include/linux/pps.h
> > > @@ -22,6 +22,8 @@
> > >  #ifndef _PPS_H_
> > >  #define _PPS_H_
> > >  
> > > +#include <linux/types.h>
> > > +
> > >  #define PPS_VERSION		"5.3.6"
> > >  #define PPS_MAX_SOURCES		16		/* should be enough... */
> > 
> > That file has other issues that should be addresses too.
> > 1) It uses int rather than wide specific types
> > 2) It uses structs with questionable alignmner as per David's comment
> > 
> 
> This should be send in different patch.
> 
> > Keeping the warning until all issues are sorted out is preferred.
> > If we 'fix' the warning then we loose the reminder that this file
> > needs to be eyeballed.
> > 
> 
> You mean files which do not get headers_check warning are absolutely OK.
> This is totally insane.
> 
> This are different issues and need to send by different series of
> patches. Please do not mix up things.

If others maintainers will be like you they will never get any patch. If
they keep on saying go and fix complete source file first.

Do you get some idea, what are you requesting for.

If you find the problem why do not you submit patches ?

Thanks,
--
JSR

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/