From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755298AbbBUHSM (ORCPT ); Sat, 21 Feb 2015 02:18:12 -0500 Received: from mga11.intel.com ([192.55.52.93]:53596 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbbBUHSJ (ORCPT ); Sat, 21 Feb 2015 02:18:09 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,619,1418112000"; d="scan'208";a="655140706" Date: Sat, 21 Feb 2015 15:17:45 +0800 From: kbuild test robot To: Keith Busch Cc: kbuild-all@01.org, Matthew Wilcox , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH block] NVMe: nvme_meta_noop can be static Message-ID: <20150221071745.GA54786@lkp-sb04> References: <201502211535.pykDvoRT%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201502211535.pykDvoRT%fengguang.wu@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: fengguang.wu@intel.com X-SA-Exim-Scanned: No (on bee); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org drivers/block/nvme-core.c:2008:22: sparse: symbol 'nvme_meta_noop' was not declared. Should it be static? Signed-off-by: Fengguang Wu --- nvme-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c index 3ffa57a..384c786 100644 --- a/drivers/block/nvme-core.c +++ b/drivers/block/nvme-core.c @@ -2005,7 +2005,7 @@ static int nvme_noop_generate(struct blk_integrity_iter *iter) return 0; } -struct blk_integrity nvme_meta_noop = { +static struct blk_integrity nvme_meta_noop = { .name = "NVME_META_NOOP", .generate_fn = nvme_noop_generate, .verify_fn = nvme_noop_verify,