Linux Container Development
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: [PATCH 1/3] export generic checkpoint headers to user space
Date: Thu, 28 May 2009 18:10:51 -0500	[thread overview]
Message-ID: <1243552253-7221-1-git-send-email-ntl@pobox.com> (raw)

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>
---
 include/linux/Kbuild |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index 3f0eaa3..25b7c0e 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -44,6 +44,8 @@ header-y += bpqether.h
 header-y += bsg.h
 header-y += can.h
 header-y += cdk.h
+header-y += checkpoint_types.h
+header-y += checkpoint_hdr.h
 header-y += chio.h
 header-y += coda_psdev.h
 header-y += coff.h
-- 
1.6.0.6

             reply	other threads:[~2009-05-28 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 23:10 Nathan Lynch [this message]
     [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
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=1243552253-7221-1-git-send-email-ntl@pobox.com \
    --to=ntl-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@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