From: Sam Ravnborg <sam@ravnborg.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.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>
Subject: Re: [PATCH] headers_check fix: linux/pps.h
Date: Sat, 27 Jun 2009 23:53:46 +0200 [thread overview]
Message-ID: <20090627215346.GA2719@uranus.ravnborg.org> (raw)
In-Reply-To: <1246120414.32198.5.camel@hpdv5.satnam>
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
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.
This is not a quest to eliminate warnings - this is a quest to
raise the quality and correctness of the exported headers.
The warnings serves as reminders where to focus attention.
Sam
next prev parent reply other threads:[~2009-06-27 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 16:33 Jaswinder Singh Rajput
2009-06-27 21:53 ` Sam Ravnborg [this message]
2009-06-28 5:17 ` Jaswinder Singh Rajput
2009-06-28 5:37 ` Jaswinder Singh Rajput
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090627215346.GA2719@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=giometti@linux.it \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®