From: Vadim Kochan <vadim4j@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Vadim Kochan <vadim4j@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 2/4] ip: Allow to easy change network namespace
Date: Wed, 24 Dec 2014 22:33:22 +0200 [thread overview]
Message-ID: <20141224203322.GA9728@angus-think.lan> (raw)
In-Reply-To: <20141224123522.15370a16@urahara>
On Wed, Dec 24, 2014 at 12:35:22PM -0800, Stephen Hemminger wrote:
> On Sat, 13 Dec 2014 19:55:32 +0200
> Vadim Kochan <vadim4j@gmail.com> wrote:
>
> > From: Vadim Kochan <vadim4j@gmail.com>
> >
> > Added new '-netns' option to simplify executing following cmd:
> >
> > ip netns exec NETNS ip OPTIONS COMMAND OBJECT
> >
> > to
> >
> > ip -n[etns] NETNS OPTIONS COMMAND OBJECT
> >
> > e.g.:
> >
> > ip -net vnet0 link add br0 type bridge
> > ip -n vnet0 link
> >
> > Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
>
> Needs to be rebased against current upstream code.
> Will not apply clean any more.
>
> Please resubmit whole patch series.
And add Signed-off for Jiri as he was add it for each patch ?
next prev parent reply other threads:[~2014-12-24 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 17:55 [PATCH iproute2 0/4] Switch network ns w/o execvp for iproute2 tools Vadim Kochan
2014-12-13 17:55 ` [PATCH iproute2 1/4] lib: Add netns_switch func for change network namespace Vadim Kochan
2014-12-14 9:35 ` Jiri Pirko
2014-12-13 17:55 ` [PATCH iproute2 2/4] ip: Allow to easy " Vadim Kochan
2014-12-14 9:36 ` Jiri Pirko
2014-12-24 20:35 ` Stephen Hemminger
2014-12-24 20:33 ` Vadim Kochan [this message]
2014-12-24 21:07 ` Vadim Kochan
2014-12-13 17:55 ` [PATCH iproute2 3/4] bridge: " Vadim Kochan
2014-12-14 9:36 ` Jiri Pirko
2014-12-13 17:55 ` [PATCH iproute2 4/4] tc: " Vadim Kochan
2014-12-14 9:36 ` Jiri Pirko
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=20141224203322.GA9728@angus-think.lan \
--to=vadim4j@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).