Message-ID: <55ADD44F.60804@gmail.com>
Date: Tue, 21 Jul 2015 13:10:39 +0800
From: Kinglong Mee <kinglongmee@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "J. Bruce Fields" <bfields@fieldses.org>
CC: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
        linux-kernel@vger.kernel.org, kinglongmee@gmail.com
Subject: Re: linux-next: build failure after merge of the nfsd tree
References: <20150721095737.7411eb05@canb.auug.org.au>
In-Reply-To: <20150721095737.7411eb05@canb.auug.org.au>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1045
Lines: 33

Sorry for my fault.
Please drop the old version and use the new version 3.

thanks,
Kinglong Mee

On 7/21/2015 07:57, Stephen Rothwell wrote:
> Hi,
> 
> After merging the nfsd tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> fs/nfsd/nfs4state.c: In function 'client_has_state':
> fs/nfsd/nfs4state.c:2249:22: error: 'struct nfs4_client' has no member named 'cl_lo_states'
>    || !list_empty(&clp->cl_lo_states)
>                       ^
> fs/nfsd/nfs4state.c:2252:1: warning: control reaches end of non-void function [-Wreturn-type]
>  }
>  ^
> 
> Caused by commit
> 
>   395b297af7bf ("nfsd: Add layouts checking in client_has_state()")
> 
> cl_lo_states is only defined when CONFIG_NFSD_PNFS is set.
> 
> I have used the nsfd tree from next-20150720 for today.
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/