From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/3] export generic checkpoint headers to user space
Date: Fri, 29 May 2009 06:22:16 -0400 [thread overview]
Message-ID: <4A1FB758.2060802@cs.columbia.edu> (raw)
In-Reply-To: <20090529010217.GD17402-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Applied to ckpt-v16-dev, thanks.
Oren.
Matt Helsley wrote:
> On Thu, May 28, 2009 at 06:10:51PM -0500, Nathan Lynch wrote:
>> Checkpoint-related headers are not properly exported, resulting in
>>
>> $ make ARCH=i386 headers_check -s
>> /home/nathanl/devel/linux-2.6.git/usr/include/linux/fs.h:11: included file 'linux/checkpoint_types.h' is not exported
>>
>> Export checkpoint_types.h and checkpoint_hdr.h.
>>
>> After this and arch-specific exports to follow, user-cr can be built
>> against the result of 'make headers_install'.
>>
>> Signed-off-by: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
>> ---
>
> You can apply this to all 3:
>
> Acked-by: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>
> Thanks for posting these.
>
> Cheers,
> -Matt
>
next prev parent reply other threads:[~2009-05-29 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 23:10 [PATCH 1/3] export generic checkpoint headers to user space Nathan Lynch
[not found] ` <1243552253-7221-1-git-send-email-ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-05-28 23:10 ` [PATCH 2/3] x86: export checkpoint_hdr.h Nathan Lynch
2009-05-28 23:10 ` [PATCH 3/3] s390: " Nathan Lynch
2009-05-29 1:02 ` [PATCH 1/3] export generic checkpoint headers to user space Matt Helsley
[not found] ` <20090529010217.GD17402-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-29 10:22 ` Oren Laadan [this message]
2009-05-29 10:22 ` 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=4A1FB758.2060802@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@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 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.