From: Florian Lohoff <flo@rfc822.org>
To: linux@cthulhu.engr.sgi.com
Subject: resources.h patch / RLIM_INFINITY __KERNEL__ depend ?
Date: Thu, 30 Mar 2000 14:27:05 +0200 [thread overview]
Message-ID: <20000330142705.B3530@paradigm.rfc822.org> (raw)
Hi,
again - short patch - RLIM_INFINITY - This is also defined in
both glibc 2.0 and glibc 2.1 headers so it should be __KERNEL__
dependend - Shouldnt it ?
Index: resource.h
===================================================================
RCS file: /cvs/linux/include/asm-mips/resource.h,v
retrieving revision 1.5
diff -u -r1.5 resource.h
--- resource.h 2000/02/04 07:40:53 1.5
+++ resource.h 2000/03/30 12:19:42
@@ -25,13 +25,13 @@
#define RLIM_NLIMITS 10 /* Number of limit flavors. */
+#ifdef __KERNEL__
+
/*
* SuS says limits have to be unsigned.
* Which makes a ton more sense anyway.
*/
#define RLIM_INFINITY 0x7fffffffUL
-
-#ifdef __KERNEL__
#define INIT_RLIMITS \
{ \
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."
next reply other threads:[~2000-03-30 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 12:27 Florian Lohoff [this message]
2000-03-30 16:47 ` resources.h patch / RLIM_INFINITY __KERNEL__ depend ? Ralf Baechle
2000-03-31 8:29 ` Florian Lohoff
2000-03-31 11:46 ` Ralf Baechle
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=20000330142705.B3530@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux@cthulhu.engr.sgi.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