From: ebiederm@xmission.com (Eric W. Biederman)
To: DervishD <raul@viadomus.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: 28 Jan 2002 12:44:59 -0700 [thread overview]
Message-ID: <m18zaidzus.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E16VHV3-0001Wh-00@DervishD.viadomus.com>
In-Reply-To: <E16VHV3-0001Wh-00@DervishD.viadomus.com>
DervishD <raul@viadomus.com> writes:
> Hello all :))
>
> I've reading the source code for 'blockdev', from util-linux, and
> the comments says that the header 'linux/fs.h' cannot be included.
> I've tried, just adding an include and removing the hand made
> definitions (cloning those of fs.h), and all works ok :??
>
> This header can be included or not? It works for me, with headers
> from 2.4.17, so, is it just for backwards compatibility?
Policy. It is for forwards compatibility. The general policy on kernel
headers is that if it breaks you get to keep the pieces.
Eric
next prev parent reply other threads:[~2002-01-28 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 19:31 Why 'linux/fs.h' cannot be included? I *can* DervishD
2002-01-28 19:44 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 10:20 DervishD
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51 ` Alan Cox
2002-01-29 14:42 ` Jeff Garzik
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik
[not found] <mailman.1012391761.28301.linux-kernel2news@redhat.com>
2002-01-30 18:24 ` Pete Zaitcev
2002-01-30 23:33 ` Keith Owens
2002-01-31 1:17 ` Jeff Garzik
2002-01-31 1:51 ` Keith Owens
2002-01-31 1:57 ` Jeff Garzik
2002-01-31 2:06 ` Keith Owens
2002-01-31 2:35 ` Jeff Garzik
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=m18zaidzus.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@viadomus.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