mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: DervishD <raul@viadomus.com>
To: ebiederm@xmission.com, raul@viadomus.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: Tue, 29 Jan 2002 11:20:02 +0100	[thread overview]
Message-ID: <E16VVMw-0001oa-00@DervishD.viadomus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

    Hello Eric :)

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

    That is: I can include it if I just want the definition of a few
ioctl's, but if in a future version all that is changed or even
dissapears is completely my problem.

    Given the number of user-space apps that needs ioctl definitions
and things like those (that are supposed not to change easily), those
definitions should go in user-includable headers... IMHO.

    Fortunately, we have some of them in libc headers now.

    Thanks,
    Raúl

             reply	other threads:[~2002-01-29 10:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 10:20 DervishD [this message]
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51   ` Alan Cox
2002-01-29 14:42     ` 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
  -- strict thread matches above, loose matches on Subject: below --
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik
2002-01-28 19:31 DervishD
2002-01-28 19:44 ` Eric W. Biederman

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=E16VVMw-0001oa-00@DervishD.viadomus.com \
    --to=raul@viadomus.com \
    --cc=ebiederm@xmission.com \
    --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
Powered by JetHome