From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Monson Shao <jshao@redhat.com>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] setns: add ns_name in TINFO
Date: Thu, 17 Oct 2013 18:20:43 +0800 [thread overview]
Message-ID: <525FB9FB.8030503@cn.fujitsu.com> (raw)
In-Reply-To: <1382002005-15348-1-git-send-email-jshao@redhat.com>
On 10/17/2013 05:26 PM, Monson Shao wrote:
> Make it clear which namespace is enabled and being tested.
>
> before:
> setns01 0 TINFO : ns_fds[0]=5, ns_types[0]=0x8000000
> setns01 0 TINFO : ns_fds[1]=6, ns_types[1]=0x20000
> setns01 0 TINFO : ns_fds[2]=7, ns_types[2]=0x40000000
> setns01 0 TINFO : ns_fds[3]=8, ns_types[3]=0x20000000
> setns01 0 TINFO : ns_fds[4]=9, ns_types[4]=0x4000000
>
> after:
> setns01 0 TINFO : ns_name=ipc, ns_fds[0]=5, ns_types[0]=0x8000000
> setns01 0 TINFO : ns_name=mnt, ns_fds[1]=6, ns_types[1]=0x20000
> setns01 0 TINFO : ns_name=net, ns_fds[2]=7, ns_types[2]=0x40000000
> setns01 0 TINFO : ns_name=pid, ns_fds[3]=8, ns_types[3]=0x20000000
> setns01 0 TINFO : ns_name=uts, ns_fds[4]=9, ns_types[4]=0x4000000
>
> Signed-off-by: Monson Shao <jshao@redhat.com>
Applied, thank you.
Wanlong Gao
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-10-17 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:26 [LTP] [PATCH] setns: add ns_name in TINFO Monson Shao
2013-10-17 10:03 ` Jan Stancek
2013-10-17 10:20 ` Wanlong Gao [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=525FB9FB.8030503@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jshao@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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