From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: nfs tree build failure
Date: Mon, 01 Feb 2010 09:15:13 -0500 [thread overview]
Message-ID: <1265033714.2658.1.camel@localhost> (raw)
In-Reply-To: <20100201183838.63439783.sfr@canb.auug.org.au>
On Mon, 2010-02-01 at 18:38 +1100, Stephen Rothwell wrote:
> Hi Trond,
>
> Today's linux-next build (sparc defconfig) failed like this:
>
> fs/nfs/write.c: In function 'nfs_wb_page':
> fs/nfs/write.c:1478: error: implicit declaration of function 'nfs_commit_inode'
>
> Caused by commit d01b3158b56e292dbb3eea711a51a1d3dbec5094 ("NFS: Simplify
> nfs_wb_page()"). Neither CONFIG_NFS_V3 nor CONFIG_NFS_V4 is set in this
> build.
>
> I have reverted that commit for today.
Hi Stephen,
Sorry. There was a 1 line change that somehow slipped out of the final
revision of the patch. It should be fixed now.
Cheers
Trond
next prev parent reply other threads:[~2010-02-01 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 7:38 linux-next: nfs tree build failure Stephen Rothwell
2010-02-01 14:15 ` Trond Myklebust [this message]
2010-02-01 23:24 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-12-07 8:23 Stephen Rothwell
2009-12-07 22:32 ` Trond Myklebust
2009-12-07 22:53 ` Stephen Rothwell
2009-12-04 0:36 Stephen Rothwell
2009-03-16 10:55 Stephen Rothwell
2009-03-16 12:19 ` Trond Myklebust
2009-03-16 23:04 ` Stephen Rothwell
2009-03-12 0:26 Stephen Rothwell
2009-03-12 18:54 ` Trond Myklebust
2009-03-12 22:07 ` 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=1265033714.2658.1.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.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).