Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH user-cr] s390: define struct pid_set
Date: Fri, 18 Sep 2009 13:00:49 -0400	[thread overview]
Message-ID: <4AB3BCC1.8050803@librato.com> (raw)
In-Reply-To: <20090917034703.GA25290-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>



Serge E. Hallyn wrote:
> Assume the definition was lost in pulling this code out of
> mktree.c.

yes it was... thanks.

> 
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
>  clone_s390x.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/clone_s390x.c b/clone_s390x.c
> index 39d12e5..661a5c4 100644
> --- a/clone_s390x.c
> +++ b/clone_s390x.c
> @@ -24,6 +24,12 @@
>   */
>  #if defined(__NR_clone_with_pids)
>  
> +/* this really belongs to some kernel header ! */
> +struct pid_set {
> +	int num_pids;
> +	pid_t *pids;
> +};
> +
>  /* (see: http://lkml.indiana.edu/hypermail/linux/kernel/9604.3/0204.html) */
>  
>  #define do_clone_with_pids(stack, flags, ptid, ctid, setp) ({ \
> @@ -47,7 +53,7 @@
>  	})
>  
>  int clone_with_pids(int (*fn)(void *), void *child_stack, int flags,
> -			struct target_pid_set *target_pids, void *arg)
> +			struct pid_set *target_pids, void *arg)
>  {
>  	long retval;
>  	retval = do_clone_with_pids(child_stack, flags, NULL, NULL,

      parent reply	other threads:[~2009-09-18 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  3:47 [PATCH user-cr] s390: define struct pid_set Serge E. Hallyn
     [not found] ` <20090917034703.GA25290-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-18 17:00   ` Oren Laadan [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=4AB3BCC1.8050803@librato.com \
    --to=orenl-rdfvbdnroixbdgjk7y7tuq@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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