From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: references to non-existent header files under include/linux
Date: Sat, 13 Jun 2009 10:47:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906131042440.17932@localhost> (raw)
In-Reply-To: <20090613134947.GA30053@uranus.ravnborg.org>
On Sat, 13 Jun 2009, Sam Ravnborg wrote:
> On Sat, Jun 13, 2009 at 09:35:42AM -0400, Robert P. J. Day wrote:
> >
> > again, since this output is fairly short, this is a list of
> > references throughout the source tree of the form:
> >
> > #include <linux/whatever>
> >
> > where there does not appear to be any such header file. might be some
> > false positives but i'm not going to agonize over it.
> >
> >
> > === Missing: include/linux/bounds.h ===
> > include/linux/mmzone.h:18:#include <linux/bounds.h>
> > include/linux/page-flags.h:11:#include <linux/bounds.h>
> bounds.h is generated.
>
> > === Missing: include/linux/compile.h ===
> > arch/x86/boot/version.c:17:#include <linux/compile.h>
> > init/version.c:9:#include <linux/compile.h>
> compile.h is generated.
which i would have recognized if i hadn't been reduced to drinking
decaf this morning. *sigh*.
> The rest looks like real bugs.
> Please submit patches to fix them up.
these days, i'm more partial to just doing the scan and, when the
official time comes, passing off the results to the various subsystem
maintainers, only because sometimes it's not immediately obvious what
the correct fix is.
maybe it's a typo, maybe it's a partial feature commit where the
code should include the header file but the header file is yet to be
added, maybe it's part of code that is no longer even being compiled
due to changes in #ifdef's or Kconfig files, maybe it's for a
non-intel arch that i'm not set up to test, maybe ... anyway, you get
the idea. and, in some cases, when the subsystem maintainer takes a
look at it, it might be that that single incorrect line represents a
much larger issue that only that maintainer should deal with.
in short, i'll just be lazy and whine, and let others do the actual
fixing. :-)
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-06-13 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 13:35 references to non-existent header files under include/linux Robert P. J. Day
2009-06-13 13:49 ` Sam Ravnborg
2009-06-13 14:47 ` Robert P. J. Day [this message]
2009-06-13 22:08 ` Rafael J. Wysocki
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=alpine.LFD.2.00.0906131042440.17932@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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