From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH 3/9] user-cr: s390 eclone wrapper
Date: Wed, 18 Nov 2009 09:24:50 -0600 [thread overview]
Message-ID: <20091118152450.GB23694@us.ibm.com> (raw)
In-Reply-To: <1258520988.4031.1254.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Quoting Nathan Lynch (ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org):
> On Tue, 2009-11-17 at 21:23 -0600, Serge E. Hallyn wrote:
> > Quoting Nathan Lynch (ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org):
> > > Based on original work from Serge Hallyn.
> >
> > Needed the following patch on top of that. Otherwise the
> > whole set looks good to me, thanks!
>
> Great, thanks for the fixups.
>
>
> > (Oh, one other note, the default #ifdef for NR_eclone actually
> > is different depending on whether we're on a c/r kernel or not,
> > unfortunately :(. I'm leaving it as the non-c/r kernel value
> > for now.)
>
> Right.. I was thinking that the syscall numbers for eclone should
> precede those for checkpoint and restart in the c/r patch set. Thoughts
> on that?
Yes, I was thinking the same thing.
-serge
next prev parent reply other threads:[~2009-11-18 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:55 [PATCH 0/9] user-cr: update to eclone API; add nsexeccwp Nathan Lynch
[not found] ` <1258505746-31182-1-git-send-email-ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-11-18 0:55 ` [PATCH 1/9] user-cr: add eclone/clone_args header Nathan Lynch
2009-11-18 0:55 ` [PATCH 2/9] user-cr: x86_32 eclone wrapper Nathan Lynch
2009-11-18 0:55 ` [PATCH 3/9] user-cr: s390 " Nathan Lynch
[not found] ` <1258505746-31182-4-git-send-email-ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-11-18 3:23 ` Serge E. Hallyn
[not found] ` <20091118032333.GA18641-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-18 5:09 ` Nathan Lynch
[not found] ` <1258520988.4031.1254.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-11-18 15:24 ` Serge E. Hallyn [this message]
[not found] ` <20091118152450.GB23694-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-25 18:40 ` Oren Laadan
2009-11-18 0:55 ` [PATCH 4/9] user-cr: ppc32 " Nathan Lynch
[not found] ` <1258505746-31182-5-git-send-email-ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-11-19 16:18 ` Nathan Lynch
2009-11-18 0:55 ` [PATCH 5/9] user-cr: add nsexeccwp to test eclone Nathan Lynch
2009-11-18 0:55 ` [PATCH 6/9] user-cr: use eclone API for restart Nathan Lynch
2009-11-18 0:55 ` [PATCH 7/9] user-cr: remove x86_32 clone_with_pids Nathan Lynch
2009-11-18 0:55 ` [PATCH 8/9] user-cr: remove s390 clone_with_pids Nathan Lynch
2009-11-18 0:55 ` [PATCH 9/9] user-cr: remove powerpc clone_with_pids Nathan Lynch
2009-11-25 18:41 ` [PATCH 0/9] user-cr: update to eclone API; add nsexeccwp Oren Laadan
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=20091118152450.GB23694@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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