lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 13 Oct 2015 20:58:44 +0800
From:	Fengguang Wu <lkp@...el.com>
To:	Alim Akhtar <alim.akhtar@...sung.com>
Cc:	devicetree@...r.kernel.org, linux-scsi@...r.kernel.org,
	JBottomley@...n.com, linux-kernel@...r.kernel.org,
	Kishon Vijay Abraham I <kishon@...com>,
	amit.daniel@...sung.com, kbuild-all@...org, vinholikatti@...il.com,
	essuuj@...il.com
Subject: Re: [kbuild-all] [RFC PATCH] phy: exynos-ufs:
 exynos_ufs_phy_calibrate() can be static

On Tue, Oct 13, 2015 at 05:08:58PM +0530, Alim Akhtar wrote:
> HI
> How I am support to handle this patch? Should I just fix these warnings in
> my patch or I just add this as a separate patch on the top of the series?

Alim, you can simply fold it into your patch.

Thanks,
Fengguang

> On 10/01/2015 04:34 PM, kbuild test robot wrote:
> >
> >Signed-off-by: Fengguang Wu <fengguang.wu@...el.com>
> >---
> >  phy-exynos-ufs.c |    6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> >diff --git a/drivers/phy/phy-exynos-ufs.c b/drivers/phy/phy-exynos-ufs.c
> >index 343fcaf..835ee78 100644
> >--- a/drivers/phy/phy-exynos-ufs.c
> >+++ b/drivers/phy/phy-exynos-ufs.c
> >@@ -66,7 +66,7 @@ static bool match_cfg_to_pwr_mode(u8 desc, u8 required_pwr)
> >  	return false;
> >  }
> >
> >-int exynos_ufs_phy_calibrate(struct phy *phy, enum phy_cfg_tag tag, u8 pwr)
> >+static int exynos_ufs_phy_calibrate(struct phy *phy, enum phy_cfg_tag tag, u8 pwr)
> >  {
> >  	struct exynos_ufs_phy *ufs_phy = get_exynos_ufs_phy(phy);
> >  	struct exynos_ufs_phy_cfg **cfgs = ufs_phy->cfg;
> >@@ -93,14 +93,14 @@ out:
> >  	return 0;
> >  }
> >
> >-void exynos_ufs_phy_set_lane_cnt(struct phy *phy, u8 lane_cnt)
> >+static void exynos_ufs_phy_set_lane_cnt(struct phy *phy, u8 lane_cnt)
> >  {
> >  	struct exynos_ufs_phy *ufs_phy = get_exynos_ufs_phy(phy);
> >
> >  	ufs_phy->lane_cnt = lane_cnt;
> >  }
> >
> >-int exynos_ufs_phy_wait_for_lock_acq(struct phy *phy)
> >+static int exynos_ufs_phy_wait_for_lock_acq(struct phy *phy)
> >  {
> >  	struct exynos_ufs_phy *ufs_phy = get_exynos_ufs_phy(phy);
> >  	const unsigned int timeout_us = 100000;
> >
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@...ts.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ