From: Jeff Garzik <garzik@havoc.gtf.org>
To: DervishD <raul@viadomus.com>
Cc: ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: Wed, 30 Jan 2002 11:12:33 -0500 [thread overview]
Message-ID: <20020130111233.A21325@havoc.gtf.org> (raw)
In-Reply-To: <E16VtWb-0002kV-00@DervishD.viadomus.com>
In-Reply-To: <E16VtWb-0002kV-00@DervishD.viadomus.com>; from raul@viadomus.com on Wed, Jan 30, 2002 at 01:07:37PM +0100
On Wed, Jan 30, 2002 at 01:07:37PM +0100, DervishD wrote:
> The problem is that I don't want to copy the definitions I need
> from linux/fs.h, because this will lead to problems if those
> definitions change. Anyway this is not an issue, because by changing
> the running kernel those definitions in fact may not be valid...
>
> Resuming: I don't know how properly address this problem.
Go ahead and copy. If ioctl interfaces change, then binary
compatibility just changed too. By nature that will be changed
infrequently, if at all.
Jeff
next prev parent reply other threads:[~2002-01-30 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik [this message]
[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-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-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=20020130111233.A21325@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=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
all inboxes | Powered by JetHome®