From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: apparently missing include/linux header files
Date: Sat, 6 Oct 2007 11:51:59 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710061150090.22349@localhost.localdomain> (raw)
In-Reply-To: <8bd0f97a0710060732k423eec3ar8a6cdc64bcaf373@mail.gmail.com>
On Sat, 6 Oct 2007, Mike Frysinger wrote:
> On 10/6/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > the result of running a quick and dirty shell script that
> > locates inclusions of header files under "include/linux" where
> > those header files don't appear to exist. (i didn't look any more
> > closely at the results and, apparently, these missing header files
> > aren't fatal since the builds still work but it's just FYI.)
>
> the ones related to kgdb are "normal" ... they require the kgdb patch
> to be applied and if it isnt, then it isnt possible to build the files
> in question
well, like i said, i didn't do any sanity checking on that list, so
i'm sure there are going to be a few false positives. i just thought
i'd throw that list out there in case there was anything genuinely
problematic so it could be resolved before the next release.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
prev parent reply other threads:[~2007-10-06 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 9:47 Robert P. J. Day
2007-10-06 14:32 ` Mike Frysinger
2007-10-06 15:51 ` Robert P. J. Day [this message]
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.0710061150090.22349@localhost.localdomain \
--to=rpjday@mindspring.com \
--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®