From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756705AbdCHDPN (ORCPT ); Tue, 7 Mar 2017 22:15:13 -0500 Received: from ozlabs.org ([103.22.144.67]:55917 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756506AbdCHDO5 (ORCPT ); Tue, 7 Mar 2017 22:14:57 -0500 Date: Wed, 8 Mar 2017 10:16:43 +1100 From: Stephen Rothwell To: Miklos Szeredi Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Amir Goldstein Subject: linux-next: build warnings after merge of the overlayfs tree Message-ID: <20170308101643.0bc34e88@canb.auug.org.au> 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 Miklos, After merging the overlayfs tree, today's linux-next build (powerpc ppc64_defconfig) produced these warnings: fs/overlayfs/inode.c:322:30: warning: 'ovl_i_mutex_key' defined but not used [-Wunused-variable] static struct lock_class_key ovl_i_mutex_key[FILESYSTEM_MAX_STACK_DEPTH]; ^ fs/overlayfs/inode.c:323:30: warning: 'ovl_i_mutex_dir_key' defined but not used [-Wunused-variable] static struct lock_class_key ovl_i_mutex_dir_key[FILESYSTEM_MAX_STACK_DEPTH]; ^ Introduced by commit a41471e8eff8 ("ovl: lockdep annotate of nested stacked overlayfs inode lock") CONFIG_LOCKDEP is not set for this build. -- Cheers, Stephen Rothwell