linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, James Morris <jmorris@namei.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: next-20081114 build failure
Date: Sun, 16 Nov 2008 11:43:11 +0000	[thread overview]
Message-ID: <1852.1226835791@redhat.com> (raw)
In-Reply-To: <20081116223008.4772920e.sfr@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Today's linux-next build (mips defconfig) failed like this:
> 
> fs/nfsctl.c:45: error: implicit declaration of function 'current_cred'
> 
> This is why you need explicit includes ...

Oops.  I really need to cull the number of creds trees I've got.  I didn't
apply your patches to all of them.

David

  reply	other threads:[~2008-11-16 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 11:30 linux-next: next-20081114 build failure Stephen Rothwell
2008-11-16 11:43 ` David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-16 11:36 Stephen Rothwell
2008-11-16 20:42 ` David Miller

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=1852.1226835791@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).