The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
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:51:13 -0500	[thread overview]
Message-ID: <8bd0f97a0711052051v45856f6apfacd66ade1d47113@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711052327090.6602@localhost.localdomain>

On 11/5/07, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>   this list is short enough that i'll just post it here -- attempts to
> include header files under include/linux when those header files
> simply don't exist.  obviously, there might be false positives for one
> reason or another.

obviously the kgdb ones can be ignored

> (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

as for the Blackfin ones, the answer is the same last time you ask ...
the includes are for drivers we havent pushed to mainline yet
-mike

  reply	other threads:[~2007-11-06  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06  4:31 a list of non-existent but included include/linux header files Robert P. J. Day
2007-11-06  4:51 ` Mike Frysinger [this message]
2007-11-06  4:58   ` Robert P. J. Day
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=8bd0f97a0711052051v45856f6apfacd66ade1d47113@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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