[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201412101021.JoZosGm6%fengguang.wu@intel.com>
Date: Wed, 10 Dec 2014 10:12:49 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Alan Tull <atull@...nsource.altera.com>
Cc: kbuild-all@...org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [socfpga-nex:for_next-fpgamgr-without-overlays-v4 8/9]
drivers/staging/fpga/fpga-mgr.c:46:5: sparse: symbol
'fpga_mgr_low_level_state' was not declared. Should it be static?
tree: git://git.rocketboards.org/linux-socfpga-next for_next-fpgamgr-without-overlays-v4
head: 590b747bfa6791797c241116453acf50bc4e5dda
commit: 356ae534a603de3aa8b1cfc173a777f59273d32e [8/9] staging: fpga manager: framework core
reproduce:
# apt-get install sparse
git checkout 356ae534a603de3aa8b1cfc173a777f59273d32e
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/staging/fpga/fpga-mgr.c:46:5: sparse: symbol 'fpga_mgr_low_level_state' was not declared. Should it be static?
>> drivers/staging/fpga/fpga-mgr.c:324:30: sparse: symbol 'fpga_mgr_groups' was not declared. Should it be static?
>> drivers/staging/fpga/fpga-mgr.c:365:25: sparse: symbol 'fpga_mgr_dev_pm_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists