From: "H. Peter Anvin" <hpa@zytor.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15-final drivers/net/bonding.c includes user space headers
Date: Sun, 25 Nov 2001 18:22:20 -0800 [thread overview]
Message-ID: <3C01A75C.3030500@zytor.com> (raw)
In-Reply-To: <1595.1006741190@ocs3.intra.ocs.com.au>
Keith Owens wrote:
>
> We already have include/linux/limits.h that is included by filesystem
> code. If anybody needs additional #defines, they can go in our version
> of limits.h instead of trying to use the gcc version.
>
I guess. I don't like the idea of not using the compiler-provided
headers, since it seems to me to make it harder to deal properly with
gcc changes, though...
-hpa
next prev parent reply other threads:[~2001-11-26 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 6:31 2.4.15-final drivers/net/bonding.c includes user space headers Keith Owens
2001-11-25 21:49 ` H. Peter Anvin
2001-11-26 2:06 ` Keith Owens
2001-11-26 2:09 ` H. Peter Anvin
2001-11-26 2:19 ` Keith Owens
2001-11-26 2:22 ` H. Peter Anvin [this message]
2001-11-26 5:02 ` David S. Miller
2001-11-26 17:55 ` Thomas Davis
2001-11-26 18:57 ` David S. Miller
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=3C01A75C.3030500@zytor.com \
--to=hpa@zytor.com \
--cc=kaos@ocs.com.au \
--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