public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [ANNOUNCE] headercheck - check dependencies on header files
Date: Fri, 10 Apr 2009 07:43:31 +0200	[thread overview]
Message-ID: <20090410054331.GB20005@uranus.ravnborg.org> (raw)
In-Reply-To: <1239334100.3036.14.camel@ht.satnam>

On Fri, Apr 10, 2009 at 08:58:20AM +0530, Jaswinder Singh Rajput wrote:
> Hello Sam,
> 
> On Thu, 2009-04-09 at 22:42 +0200, Sam Ravnborg wrote:
> > We have at several occasions discussed if our header files
> > should include their dependencies or not.
> > 
> > But we were lacking a tool to tell us if our header files
> > included the headerfiles they needed or not.
> > 
> > headercheck can be used to do so.
> > 
> > headercheck use the existing Kbuild files in
> > include/ to determine which directories to visit.
> > 
> > And for each directory it create one .c file for each
> > .h file and build it.
> > 
> > A .c file looks like this:
> > 
> > 	$cat module.h.c
> > 		#include <linux/module.h>
> > 
> 
> Is it possible to check that which header files are included in source
> file.
> 
> I mean how many header files are included for kernel/module.c and in
> which order and we can also check that same file is requested how many
> times, like:
> 
> 	linux/module.h (requested count, included or not)
> 	+linux/list.h
> 	++linux/stddef.h

Try to take a look at:
http://www.kernel.org/pub/linux/kernel/people/rayl/headergraphs/

and

http://www.kernel.org/pub/linux/kernel/people/acme/hviz

	Sam

  reply	other threads:[~2009-04-10  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 20:42 [ANNOUNCE] headercheck - check dependencies on header files Sam Ravnborg
2009-04-10  3:28 ` Jaswinder Singh Rajput
2009-04-10  5:43   ` Sam Ravnborg [this message]
2009-04-10 12:08 ` Ingo Molnar

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=20090410054331.GB20005@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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