linux-kernel - Re: [PATCH 2/2] staging: lustre: declare internal symbols as static

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]

Message-ID: <54BBB9F4.1010404@lucaceresoli.net>
Date:	Sun, 18 Jan 2015 14:49:40 +0100
From:	Luca Ceresoli <luca@...aceresoli.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>,
	Srikrishan Malik <srikrishanmalik@...il.com>,
	devel@...verdev.osuosl.org, Peng Tao <bergwolf@...il.com>,
	linux-kernel@...r.kernel.org, HPDD-discuss@...ts.01.org,
	Jinshan Xiong <jinshan.xiong@...el.com>
Subject: Re: [PATCH 2/2] staging: lustre: declare internal symbols as static

Dear Greg,

Greg Kroah-Hartman wrote:
> On Tue, Jan 13, 2015 at 11:33:03PM +0100, Luca Ceresoli wrote:
>> Fixes dozens of sparse warnings like:
>>    warning: symbol 'cfs_tracefile_sem' was not declared. Should it be static?
>>
>> Signed-off-by: Luca Ceresoli <luca@...aceresoli.net>
>> Cc: Peng Tao <bergwolf@...il.com>
>> Cc: Jinshan Xiong <jinshan.xiong@...el.com>
>> Cc: Srikrishan Malik <srikrishanmalik@...il.com>
>> Cc: HPDD-discuss@...ts.01.org
>> Cc: devel@...verdev.osuosl.org
>> Cc: linux-kernel@...r.kernel.org
>
> This patch fails to apply to my staging-next branch, sorry :(

Some of my fixes were done by somebody else in the meantime.

Several people are sending small fixes for staging every day.
So, to reduce the probability of further conflicts, I'm resending
this patch as a set of smaller ones.

-- 
Luca
--
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/