From: Clifford Wolf <clifford@clifford.at>
To: Hugh Dickins <hugh@veritas.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add rlimits to /proc/<PID>/status
Date: Sat, 31 May 2008 00:50:32 +0200 [thread overview]
Message-ID: <20080530225032.GH1369@clifford.at> (raw)
In-Reply-To: <Pine.LNX.4.64.0805302232430.31527@blonde.site>
Hi,
On Fri, May 30, 2008 at 10:35:27PM +0100, Hugh Dickins wrote:
> Aren't they better staying in /proc/<PID>/limits?
this was a cleanup of a patch I've sent to lkml about 6 months ago
when there was no yet-released (non-rc) kernel with /proc/<PID>/limits ...
my patch is a more or less duplicate of commit d85f50d5. oops.
please simply ignore it.. ;-)
yours,
- clifford
--
A byte walks into a bar and orders a pint. Bartender asks him "What's wrong?"
Byte says "Parity error." Bartender nods and says "Yeah, I thought you looked
a bit off."
next prev parent reply other threads:[~2008-05-30 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 20:11 Clifford Wolf
2008-05-30 21:35 ` Hugh Dickins
2008-05-30 22:50 ` Clifford Wolf [this message]
2008-05-30 21:46 ` Peter Zijlstra
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=20080530225032.GH1369@clifford.at \
--to=clifford@clifford.at \
--cc=hugh@veritas.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®