From: Tom Rini <trini@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.11-rc2] Move <linux/prio_tree.h> down in <linux/fs.h>
Date: Wed, 2 Feb 2005 09:34:21 -0700 [thread overview]
Message-ID: <20050202163421.GC15359@smtp.west.cox.net> (raw)
In-Reply-To: <1107361283.12383.0.camel@localhost.localdomain>
On Wed, Feb 02, 2005 at 04:21:23PM +0000, David Woodhouse wrote:
> On Tue, 2005-02-01 at 09:06 -0700, Tom Rini wrote:
> > <linux/prio_tree.h> is unsafe for inclusion by userland apps, but it
> > is in the userland-exposed portion of <linux/fs.h>. It's only needed
> > in the __KERNEL__ protected portion of the file, so move the #include
> > down to there.
>
> You accidentally posted this patch to the kernel list, not to the
> maintainers of the libc-kernelheaders package. And you might as well
> just remove the offending #include rather than moving it to a section of
> the file which is never used.
Ignoring your hint for a moment, since __KERNEL__ is still scattered all
over the place, and I haven't see anything (changeset-wise) adding "You
must use libc-kernelheaders now" in Documentation/feature-removal-schedule.txt
this is still an actual problem. Thanks.
Feel free to correct me by getting something added to
Documentation/feature-removal-schedule.txt :)
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-02-02 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 16:06 Tom Rini
2005-02-02 16:21 ` David Woodhouse
2005-02-02 16:34 ` Tom Rini [this message]
2005-02-02 18:00 ` Tom Rini
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=20050202163421.GC15359@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®