From: ebiederm@xmission.com (Eric W. Biederman)
To: "Denis V. Lunev" <den@openvz.org>
Cc: davem@davemloft.net, containers@lists.osdl.org,
netdev@vger.kernel.org, dlezcano@fr.ibm.com
Subject: Re: [PATCH 2.6.25 6/6] net: consolidate net namespace related proc files creation
Date: Mon, 19 Nov 2007 13:15:19 -0700 [thread overview]
Message-ID: <m1lk8uuh48.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20071115160150.GA25520@iris.sw.ru> (Denis V. Lunev's message of "Thu, 15 Nov 2007 19:01:50 +0300")
"Denis V. Lunev" <den@openvz.org> writes:
> net: consolidate net namespace related proc files creation
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Looks good to me, and it looks like there are a lot more places
we can use this as more code is converted.
Eric
next prev parent reply other threads:[~2007-11-19 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 16:01 [PATCH 2.6.25 6/6] net: consolidate net namespace related proc files creation Denis V. Lunev
2007-11-19 20:15 ` Eric W. Biederman [this message]
2007-11-20 6:33 ` David Miller
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=m1lk8uuh48.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).