From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [linux-cr PATCH 1/1] update x86-64 eclone and cr syscall numbers
Date: Fri, 25 Mar 2011 22:06:14 -0400 [thread overview]
Message-ID: <4D8D4A16.3080908@cs.columbia.edu> (raw)
In-Reply-To: <20110214164644.GA16802@localhost>
Pulled for v23-rc2... thanks.
Oren.
On 02/14/2011 11:46 AM, Serge E. Hallyn wrote:
> (for ckpt-v23-rc1-pids branch)
>
> Signed-off-by: Serge E. Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> ---
> arch/x86/include/asm/unistd_64.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/unistd_64.h b/arch/x86/include/asm/unistd_64.h
> index 706d90a..f5d1b9e 100644
> --- a/arch/x86/include/asm/unistd_64.h
> +++ b/arch/x86/include/asm/unistd_64.h
> @@ -671,9 +671,9 @@ __SYSCALL(__NR_fanotify_mark, sys_fanotify_mark)
> __SYSCALL(__NR_prlimit64, sys_prlimit64)
> #define __NR_eclone 303
> __SYSCALL(__NR_eclone, stub_eclone)
> -#define __NR_checkpoint 301
> +#define __NR_checkpoint 304
> __SYSCALL(__NR_checkpoint, stub_checkpoint)
> -#define __NR_restart 302
> +#define __NR_restart 305
> __SYSCALL(__NR_restart, stub_restart)
>
> #ifndef __NO_STUBS
prev parent reply other threads:[~2011-03-26 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 16:46 [linux-cr PATCH 1/1] update x86-64 eclone and cr syscall numbers Serge E. Hallyn
2011-03-26 2:06 ` 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=4D8D4A16.3080908@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@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