From: Christoph Hellwig <hch@ns.caldera.de>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Christoph Hellwig <hch@ns.caldera.de>,
Alexander Zarochentcev <zam@namesys.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Hans Reiser <reiser@namesys.com>,
reiserfs-dev@namesys.com
Subject: Re: [PATCH] reiserfs patch for linux-2.4.2
Date: Thu, 1 Mar 2001 09:18:03 +0100 [thread overview]
Message-ID: <20010301091803.A31546@caldera.de> (raw)
In-Reply-To: <20010228202733.A18073@caldera.de> <200103010316.f213G29209192@saturn.cs.uml.edu>
In-Reply-To: <200103010316.f213G29209192@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Wed, Feb 28, 2001 at 10:16:02PM -0500
On Wed, Feb 28, 2001 at 10:16:02PM -0500, Albert D. Cahalan wrote:
> Christoph Hellwig writes:
>
> > Urgg. limits.h is a userlevel header...
> >
> > The attached patch will make similar atempts fail (but not this one as
> > there is also a limits.h in gcc's include dir).
>
> There are very few files needed from gcc's include dir. Linux ought to
> be able to survive without them. Linux is already gcc-specific anyway.
I think we want stdarg.h from gcc...
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-03-01 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 19:21 [PATCH] reiserfs patch for linux-2.4.2 Alexander Zarochentcev
2001-02-28 19:27 ` Christoph Hellwig
2001-03-01 0:01 ` Keith Owens
2001-03-01 0:05 ` Christoph Hellwig
2001-03-01 3:16 ` Albert D. Cahalan
2001-03-01 8:18 ` Christoph Hellwig [this message]
2001-03-02 0:35 ` Albert D. Cahalan
2001-03-01 0:39 ` Erik Mouw
2001-03-01 10:36 ` [reiserfs-dev] " Alexander Zarochentcev
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=20010301091803.A31546@caldera.de \
--to=hch@ns.caldera.de \
--cc=acahalan@cs.uml.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=zam@namesys.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