public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Graphic: userspace headers interdependencies
Date: Sun, 23 Jul 2006 12:15:23 +0200	[thread overview]
Message-ID: <20060723101523.GS25367@stusta.de> (raw)

I've written a quick'n'dirty script for visualizing the 
interdependencies of the i386 userspace headers in 2.6.18-rc2.

In case anyone is interested, it's at [1] (warning: it's big).

The graphic also shows some problems like headers including not exported 
headers. I'm currently working on fixing such issues in my hdrcleanup 
tree.

cu
Adrian

[1] http://ftp.kernel.org/pub/linux/kernel/people/bunk/hdrcleanup/graphics/userspace-headers-i386-2.6.18-rc2.png

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2006-07-23 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23 10:15 Adrian Bunk [this message]
2006-07-23 15:25 ` Graphic: userspace headers interdependencies Alexey Dobriyan
2006-07-23 15:59   ` Adrian Bunk

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=20060723101523.GS25367@stusta.de \
    --to=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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