Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: Linux Containers <containers@lists.osdl.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	David Howells <dhowells@redhat.com>,
	linux-security-module@vger.kernel.org,
	Andrew Morgan <morgan@kernel.org>
Subject: [PATCH 1/8] cred: #include init.h in cred.h
Date: Mon, 1 Jun 2009 17:21:41 -0500	[thread overview]
Message-ID: <20090601222141.GA29460@us.ibm.com> (raw)
In-Reply-To: <20090601222119.GB29164@us.ibm.com>

cred.h can't be included as first header because it uses __init and
doesn't include init.h which is enough to break compilation on at least
ia64.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
 include/linux/cred.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/include/linux/cred.h b/include/linux/cred.h
index 3282ee4..4fa9996 100644
--- a/include/linux/cred.h
+++ b/include/linux/cred.h
@@ -13,6 +13,7 @@
 #define _LINUX_CRED_H
 
 #include <linux/capability.h>
+#include <linux/init.h>
 #include <linux/key.h>
 #include <asm/atomic.h>
 
-- 
1.6.1


  reply	other threads:[~2009-06-01 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 22:21 [PATCH 0/8] Credentials c/r: introduction Serge E. Hallyn
2009-06-01 22:21 ` Serge E. Hallyn [this message]
2009-06-01 22:21 ` [PATCH 2/8] groups: move code to kernel/groups.c Serge E. Hallyn
2009-06-01 22:21 ` [PATCH 3/8] cr: break out new_user_ns() Serge E. Hallyn
2009-06-01 22:22 ` [PATCH 4/8] cr: split core function out of some set*{u,g}id functions Serge E. Hallyn
2009-06-01 22:22 ` [PATCH 5/8] cr: ipc: reset kern_ipc_perms Serge E. Hallyn
2009-06-01 22:22 ` [PATCH 6/8] cr: capabilities: define checkpoint and restore fns Serge E. Hallyn
2009-06-01 22:22 ` [PATCH 7/8] cr: checkpoint and restore task credentials Serge E. Hallyn
2009-06-01 22:22 ` [PATCH 8/8] cr: restore file->f_cred Serge E. Hallyn

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=20090601222141.GA29460@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=containers@lists.osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=orenl@cs.columbia.edu \
    /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