From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@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 1/1] cr: s390: define CKPT_ARCH_ID for s390
Date: Fri, 29 May 2009 06:16:52 -0400 [thread overview]
Message-ID: <4A1FB614.6070506@cs.columbia.edu> (raw)
In-Reply-To: <20090528174503.GA22373-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
applied, thanks.
Serge E. Hallyn wrote:
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
> arch/s390/include/asm/checkpoint_hdr.h | 5 +++++
> include/linux/checkpoint_hdr.h | 1 +
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/arch/s390/include/asm/checkpoint_hdr.h b/arch/s390/include/asm/checkpoint_hdr.h
> index 185194b..fc0ace8 100644
> --- a/arch/s390/include/asm/checkpoint_hdr.h
> +++ b/arch/s390/include/asm/checkpoint_hdr.h
> @@ -20,6 +20,11 @@
> #include <sys/user.h>
> #endif
>
> +#ifdef CONFIG_64BIT
> +#define CKPT_ARCH_ID CKPT_ARCH_S390X
> +/* else - if we ever support 32bit - CKPT_ARCH_S390 */
> +#endif
> +
> /*
> * Notes
> * NUM_GPRS defined in <asm/ptrace.h> to be 16
> diff --git a/include/linux/checkpoint_hdr.h b/include/linux/checkpoint_hdr.h
> index 46f38f3..7f4972b 100644
> --- a/include/linux/checkpoint_hdr.h
> +++ b/include/linux/checkpoint_hdr.h
> @@ -89,6 +89,7 @@ enum {
> /* architecture */
> enum {
> CKPT_ARCH_X86_32 = 1,
> + CKPT_ARCH_S390X,
> };
>
> /* shared objrects (objref) */
prev parent reply other threads:[~2009-05-29 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 17:45 [PATCH 1/1] cr: s390: define CKPT_ARCH_ID for s390 Serge E. Hallyn
[not found] ` <20090528174503.GA22373-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-29 10:16 ` 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=4A1FB614.6070506@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@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