From: Cong Wang <xiyou.wangcong@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Vasiliy Kulikov <segoon@openwall.com>,
David Rientjes <rientjes@google.com>
Subject: Re: [Patch v2] proc: clean up /proc/<pid>/environ handling
Date: Wed, 04 Apr 2012 13:58:45 +0800 [thread overview]
Message-ID: <4F7BE315.6030305@gmail.com> (raw)
In-Reply-To: <20120403150225.GA6152@redhat.com>
On 04/03/2012 11:02 PM, Oleg Nesterov wrote:
>
> Again, this is identical with mem_release(), proc_environ_operations
> can simply use it instead.
>
Yeah, I noticed that, just not sure about it is worth effort to unify 2
functions... :-/ As you prefer, I will do that.
Thanks.
prev parent reply other threads:[~2012-04-04 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120328153936.495f567a.akpm@linux-foundation.org>
2012-04-03 8:28 ` [Patch v2] proc: clean up /proc/<pid>/environ handling Cong Wang
2012-04-03 15:02 ` Oleg Nesterov
2012-04-04 5:58 ` Cong Wang [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=4F7BE315.6030305@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=segoon@openwall.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).