From: David Miller <davem@davemloft.net>
To: lve@guap.ru
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bugfix: network namespace & device dummy
Date: Mon, 17 Dec 2012 11:13:36 -0800 (PST) [thread overview]
Message-ID: <20121217.111336.1116224157525741208.davem@davemloft.net> (raw)
In-Reply-To: <50CF1797.803@guap.ru>
From: "V. Lavrov" <lve@guap.ru>
Date: Mon, 17 Dec 2012 17:01:11 +0400
> If container has a network device dummyX (with lxc.network.type =
> phys), then it disappears from the system after you close the
> container.
> The patch returns the device dummyX to the initial network namespace
> after container is closed.
>
> Signed-off-by: Vitaly Lavrov <lve@guap.ru>
This patch is mangled by your email client.
Do not submit any new patches until you can successfully email
them to yourself, then successfully apply the patch that you
receive in that email.
Because that is exactly what you are asking us to do.
prev parent reply other threads:[~2012-12-17 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 13:01 [PATCH] bugfix: network namespace & device dummy V. Lavrov
2012-12-17 17:25 ` Vitaly E. Lavrov
2012-12-17 19:13 ` David Miller [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=20121217.111336.1116224157525741208.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lve@guap.ru \
--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).