All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Monson Shao <jshao@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCHv2 3/3] pidns16: child should not get parent pid in parent NS
Date: Thu, 03 Jan 2013 11:12:49 +0800	[thread overview]
Message-ID: <50E4F731.5050502@cn.fujitsu.com> (raw)
In-Reply-To: <1356511717-31058-3-git-send-email-jshao@redhat.com>

On 12/26/2012 04:48 PM, Monson Shao wrote:
> parent pid in parent NS is invisible to child, even when child got signalled
> from parent, the signaller process should be fake parent (PID 0).
> 
> Signed-off-by: Monson Shao <jshao@redhat.com>

Applied, thank you.

Wanlong Gao


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2013-01-03  3:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-25  7:26 [LTP] [PATCH 1/3] pidns16: split test condition and result judge Monson Shao
2012-12-26  6:11 ` Wanlong Gao
2012-12-26  8:48 ` [LTP] [PATCHv2 " Monson Shao
2013-01-03  3:12   ` Wanlong Gao
2013-01-03  3:14   ` Wanlong Gao
2012-12-26  8:48 ` [LTP] [PATCHv2 2/3] pidns16: modified test results Monson Shao
2013-01-03  3:12   ` Wanlong Gao
2012-12-26  8:48 ` [LTP] [PATCHv2 3/3] pidns16: child should not get parent pid in parent NS Monson Shao
2013-01-03  3:12   ` 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=50E4F731.5050502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.