From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
NeilBrown <neilb@suse•de>
Subject: linux-next: nfs tree build failure
Date: Fri, 4 Dec 2009 11:36:50 +1100 [thread overview]
Message-ID: <20091204113650.0776ce8f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Hi Trond,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/nfs/nfs4proc.c: In function 'nfs4_handle_exception':
fs/nfs/nfs4proc.c:282: error: 'err' undeclared (first use in this function)
Caused by commit b3508de20f0fc48f5e597b189eed930343ed1441
("NFS4ERR_FILE_OPEN handling in Linux/NFS").
Please, please build test, at least, *before* you publish a tree that is
included in linux-next. I have used the nfs tree from next-20091203 for
today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-12-04 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 0:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 7:38 linux-next: nfs tree build failure Stephen Rothwell
2010-02-01 14:15 ` Trond Myklebust
2010-02-01 23:24 ` Stephen Rothwell
2009-12-07 8:23 Stephen Rothwell
2009-12-07 22:32 ` Trond Myklebust
2009-12-07 22:53 ` 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=20091204113650.0776ce8f.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=neilb@suse$(echo .)de \
--cc=trond.myklebust@fys$(echo .)uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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