From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Marco Costalba <mcostalba@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: List of possible duplicated include files in include/
Date: Sun, 4 Nov 2007 13:48:17 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711041347001.12818@localhost.localdomain> (raw)
In-Reply-To: <e5bfff550711041044p7c07c42g836461e81a6005a@mail.gmail.com>
On Sun, 4 Nov 2007, Marco Costalba wrote:
> Here the number of false positives is overhelming, but perhaps there
> are also _real_ duplicated include somewhere in the bunch:
>
> include/acpi/acpi_bus.h:
> #include <linux/device.h>
... snip header file output ...
i deliberately left out header files from my script output. i can
tweak the script and add this to the web page as well.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-11-04 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 18:44 Marco Costalba
2007-11-04 18:48 ` Robert P. J. Day [this message]
2007-11-04 18:52 ` Marco Costalba
2007-11-04 19:01 ` Robert P. J. Day
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=Pine.LNX.4.64.0711041347001.12818@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mcostalba@gmail.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®