All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: dhowells@redhat.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for October 16
Date: Thu, 16 Oct 2008 23:22:06 +0100	[thread overview]
Message-ID: <19912.1224195726@redhat.com> (raw)
In-Reply-To: <20081016184118.GA19976@x200.localdomain>

Alexey Dobriyan <adobriyan@gmail.com> wrote:

> +#include <linux/cred.h>
>  #include <linux/types.h>
>  #include <linux/file.h>
>  #include <linux/fs.h>
> @@ -13,6 +14,7 @@
>  #include <linux/linkage.h>
>  #include <linux/namei.h>
>  #include <linux/mount.h>
> +#include <linux/sched.h>

Only the latter addition should be necessary.  linux/sched.h #includes
linux/cred.h.

David

  reply	other threads:[~2008-10-16 22:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 10:18 linux-next: Tree for October 16 Stephen Rothwell
2008-10-16 10:40 ` Stephen Rothwell
     [not found] ` <20081016211811.a523c8f2.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-10-16 13:47   ` Alexey Dobriyan
2008-10-16 18:41 ` Alexey Dobriyan
2008-10-16 22:22   ` David Howells [this message]
2008-10-16 19:23 ` [PATCH] linux-next: Tree for October 16 - build failure at MAL support on powerpc Kamalesh Babulal
2008-10-16 19:27   ` Josh Boyer
2008-10-16 19:58     ` Kamalesh Babulal
2008-10-16 20:42 ` [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn Kamalesh Babulal
2008-10-17  6:55   ` Jens Axboe
2008-10-17 10:24     ` Kamalesh Babulal
2008-10-17 10:57       ` Jens Axboe
2008-10-17 13:15         ` Stephen Rothwell
2008-10-17 13:37           ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2009-10-16  6:01 linux-next: Tree for October 16 Stephen Rothwell
2009-10-16 18:11 ` Kevin Hilman
2009-10-17 13:18   ` Stephen Rothwell

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=19912.1224195726@redhat.com \
    --to=dhowells@redhat.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.