From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753874AbcAHAOa (ORCPT ); Thu, 7 Jan 2016 19:14:30 -0500 Received: from ozlabs.org ([103.22.144.67]:51256 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753000AbcAHAO3 (ORCPT ); Thu, 7 Jan 2016 19:14:29 -0500 Date: Fri, 8 Jan 2016 11:14:27 +1100 From: Stephen Rothwell To: Trond Myklebust Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Benjamin Coddington Subject: linux-next: build failure after merge of the nfs tree Message-ID: <20160108111427.0b435d4d@canb.auug.org.au> X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Trond, After merging the nfs tree, today's linux-next build (arm multi_v7_defconfig) failed like this: write.c:(.text+0xa60): multiple definition of `nfs_wait_atomic_killable' fs/nfs/inode.o:inode.c:(.text+0x20a4): first defined here Caused by commit fa5cca9f3334 ("NFS: Use wait_on_atomic_t() for unlock after readahead") I have used the nfs tree from next-20160107 for today. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au