From: "Kevin P. Fleming" <kpfleming@cox.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test5 _IOR/_IOW changes are breaking userspace
Date: Fri, 12 Sep 2003 11:33:09 -0700 [thread overview]
Message-ID: <3F621165.8040207@cox.net> (raw)
In-Reply-To: <3F620E7B.4090706@cox.net>
Kevin P. Fleming wrote:
> The worst part is that the
> changes required to get the apps to compile are incompatible with all
> previous kernel headers.
>
It seems I overreacted here a bit, mea culpa...
It may just be that the new headers are enforcing proper usage, and
that the applications that won't compile are actually broken. I did
not originally suspect this given the provenance of the applications I
was dealing with, but I guess everyone makes mistakes, myself included :-)
prev parent reply other threads:[~2003-09-12 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 18:20 2.6.0-test5 _IOR/_IOW changes are breaking userspace Kevin P. Fleming
2003-09-12 18:33 ` Kevin P. Fleming [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=3F621165.8040207@cox.net \
--to=kpfleming@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.