From: Chris Wright <chrisw@osdl.org>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
Chris Wright <chrisw@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] consolidate arch specific resource.h headers
Date: Tue, 18 Jan 2005 22:49:57 -0800 [thread overview]
Message-ID: <20050118224957.I24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050119011950.GA15685@ti64.telemetry-investments.com>; from brugolsky@telemetry-investments.com on Tue, Jan 18, 2005 at 08:19:50PM -0500
* Bill Rugolsky Jr. (brugolsky@telemetry-investments.com) wrote:
> On Tue, Jan 18, 2005 at 04:10:56PM -0800, Chris Wright wrote:
> > +#define INIT_RLIMITS \
> > +{ \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { _STK_LIM, _STK_LIM_MAX }, \
> > + { 0, RLIM_INFINITY }, \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { 0, 0 }, \
> > + { INR_OPEN, INR_OPEN }, \
> > + { MLOCK_LIMIT, MLOCK_LIMIT }, \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { RLIM_INFINITY, RLIM_INFINITY }, \
> > + { MAX_SIGPENDING, MAX_SIGPENDING }, \
> > + { MQ_BYTES_MAX, MQ_BYTES_MAX }, \
> > +}
>
> While you are rooting around in there, perhaps this block
> should be converted to C99 initializer syntax, to avoid
> problems if arch-specific changes are later introduced?
Yes, I had considered the same. I had checked a couple arches and with
proper designated initializers, that bit would not need to be duplicated.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-01-19 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 0:10 Chris Wright
2005-01-19 1:19 ` Bill Rugolsky Jr.
2005-01-19 6:49 ` Chris Wright [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=20050118224957.I24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=brugolsky@telemetry-investments.com \
--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
all inboxes | Powered by JetHome®