From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: a list of non-existent but included include/linux header files
Date: Mon, 5 Nov 2007 23:58:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711052355490.21645@localhost.localdomain> (raw)
In-Reply-To: <8bd0f97a0711052051v45856f6apfacd66ade1d47113@mail.gmail.com>
On Mon, 5 Nov 2007, Mike Frysinger wrote:
> > (the only manual culling i did of the list was to remove
> > inclusions of autoconf.h and utsrelease.h -- i assumed those
> > weren't an issue for anyone.)
>
> should do the opposite ... nobody should be including
> linux/autoconf.h
ah, good point:
$ grep -r "<linux/autoconf.h>" *
arch/blackfin/mm/blackfin_sram.c:#include <linux/autoconf.h>
arch/blackfin/mach-common/interrupt.S:#include <linux/autoconf.h>
arch/mips/au1000/common/gpio.c:#include <linux/autoconf.h>
arch/m68knommu/lib/memcpy.c:#include <linux/autoconf.h>
drivers/char/mxser_new.c:#include <linux/autoconf.h>
drivers/char/mxser.c:#include <linux/autoconf.h>
drivers/ide/pci/delkin_cb.c:#include <linux/autoconf.h>
drivers/firmware/dmi-id.c:#include <linux/autoconf.h>
drivers/spi/spi.c:#include <linux/autoconf.h>
drivers/misc/fujitsu-laptop.c:#include <linux/autoconf.h>
drivers/misc/asus-laptop.c:#include <linux/autoconf.h>
drivers/misc/msi-laptop.c:#include <linux/autoconf.h>
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-06 5:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 4:31 Robert P. J. Day
2007-11-06 4:51 ` Mike Frysinger
2007-11-06 4:58 ` Robert P. J. Day [this message]
2007-11-06 5:08 ` Mike Frysinger
2007-11-06 5:35 ` Adrian Bunk
2007-11-06 10:56 ` Jesper Nilsson
2007-11-06 14:08 ` Jörn Engel
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.0711052355490.21645@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@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®