From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756072AbbJALFi (ORCPT <rfc822;w@1wt.eu>);
	Thu, 1 Oct 2015 07:05:38 -0400
Received: from mga01.intel.com ([192.55.52.88]:43874 "EHLO mga01.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754560AbbJALFd (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 1 Oct 2015 07:05:33 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.17,617,1437462000"; 
   d="scan'208";a="572018433"
Date: Thu, 1 Oct 2015 19:04:30 +0800
From: kbuild test robot <lkp@intel.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: kbuild-all@01.org, linux-scsi@vger.kernel.org,
        linux-kernel@vger.kernel.org, JBottomley@odin.com,
        vinholikatti@gmail.com, amit.daniel@samsung.com, essuuj@gmail.com,
        devicetree@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v3 02/13] phy: exynos-ufs: add UFS PHY driver for EXYNOS
 SoC
Message-ID: <201510011920.tppZbk0e%fengguang.wu@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1443686970-28104-3-git-send-email-alim.akhtar@samsung.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
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: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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