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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ceb5d977-afd2-a21a-11b8-e5f426288c68@huawei.com>
Date:   Thu, 11 Apr 2019 20:25:24 +0800
From:   YueHaibing <yuehaibing@...wei.com>
To:     Thierry Reding <thierry.reding@...il.com>
CC:     <jonathanh@...dia.com>, <digetx@...il.com>, <jroedel@...e.de>,
        <linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH -next] memory: tegra: Make terga20_mc_reset_ops static

On 2019/4/11 17:33, Thierry Reding wrote:
> On Wed, Apr 10, 2019 at 10:04:50PM +0800, Yue Haibing wrote:
>> From: YueHaibing <yuehaibing@...wei.com>
>>
>> Fix sparse warning:
>>
>> drivers/memory/tegra/tegra20.c:277:33: warning:
>>  symbol 'terga20_mc_reset_ops' was not declared. Should it be static?
>>
>> Reported-by: Hulk Robot <hulkci@...wei.com>
>> Signed-off-by: YueHaibing <yuehaibing@...wei.com>
>> ---
>>  drivers/memory/tegra/tegra20.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Applied thanks. I noticed that you use a slightly different name in your
> git author settings and your email setup. The only difference seems to
> be a space between the first and last name, so you may want to look into
> that to avoid having any inconsistencies.

Yeah, indeed, I will fix my git config, thanks!

> 
> Thierry
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ