From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "davem@davemloft.net" <davem@davemloft.net>
Cc: Pavel Emelianov <xemul@parallels.com>,
"ebiederm@aristanetworks.com" <ebiederm@aristanetworks.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shemminger@vyatta.com" <shemminger@vyatta.com>,
"devel@openvz.org" <devel@openvz.org>
Subject: Re: [Devel] [PATCH v2] tun: don't hold network namespace by tun sockets
Date: Mon, 12 Mar 2012 17:07:35 +0400 [thread overview]
Message-ID: <4F5DF517.7030406@parallels.com> (raw)
In-Reply-To: <20120312111826.26257.40812.stgit@localhost6.localdomain6>
Drop this patch. There will be third version.
Sorry for inconvenience.
--
Best regards,
Stanislav Kinsbursky
prev parent reply other threads:[~2012-03-12 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 11:20 [PATCH v2] tun: don't hold network namespace by tun sockets Stanislav Kinsbursky
2012-03-12 13:02 ` [Devel] " Stanislav Kinsbursky
2012-03-12 13:05 ` Stanislav Kinsbursky
2012-03-12 13:07 ` Stanislav Kinsbursky [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=4F5DF517.7030406@parallels.com \
--to=skinsbursky@parallels.com \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=ebiederm@aristanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).