[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201510011920.tppZbk0e%fengguang.wu@intel.com>
Date: Thu, 1 Oct 2015 19:04:30 +0800
From: kbuild test robot <lkp@...el.com>
To: Alim Akhtar <alim.akhtar@...sung.com>
Cc: kbuild-all@...org, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, JBottomley@...n.com,
vinholikatti@...il.com, amit.daniel@...sung.com, essuuj@...il.com,
devicetree@...r.kernel.org, Kishon Vijay Abraham I <kishon@...com>
Subject: Re: [PATCH v3 02/13] phy: exynos-ufs: add UFS PHY driver for EXYNOS
SoC
Hi Seungwon,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/phy/phy-exynos-ufs.c:69:5: sparse: symbol 'exynos_ufs_phy_calibrate' was not declared. Should it be static?
>> drivers/phy/phy-exynos-ufs.c:96:6: sparse: symbol 'exynos_ufs_phy_set_lane_cnt' was not declared. Should it be static?
>> drivers/phy/phy-exynos-ufs.c:103:5: sparse: symbol 'exynos_ufs_phy_wait_for_lock_acq' was not declared. Should it be static?
>> drivers/phy/phy-exynos-ufs.h:82:31: sparse: incorrect type in argument 1 (different address spaces)
drivers/phy/phy-exynos-ufs.h:82:31: expected struct regmap *map
drivers/phy/phy-exynos-ufs.h:82:31: got void [noderef] <asn:2>*reg_pmu
>> drivers/phy/phy-exynos-ufs.h:82:31: sparse: incorrect type in argument 1 (different address spaces)
drivers/phy/phy-exynos-ufs.h:82:31: expected struct regmap *map
drivers/phy/phy-exynos-ufs.h:82:31: got void [noderef] <asn:2>*reg_pmu
>> drivers/phy/phy-exynos-ufs.c:203:22: sparse: incorrect type in assignment (different address spaces)
drivers/phy/phy-exynos-ufs.c:203:22: expected void [noderef] <asn:2>*reg_pmu
drivers/phy/phy-exynos-ufs.c:203:22: got struct regmap *
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all 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