Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752481AbaBLO5Y (ORCPT ); Wed, 12 Feb 2014 09:57:24 -0500 Received: from mail1.windriver.com ([147.11.146.13]:36866 "EHLO mail1.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752421AbaBLO5V (ORCPT ); Wed, 12 Feb 2014 09:57:21 -0500 Message-ID: <52FB8BEB.5020506@windriver.com> Date: Wed, 12 Feb 2014 09:57:47 -0500 From: Paul Gortmaker User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: David Rientjes CC: , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Subject: Re: [PATCH] x86: fix two sparse warnings in early boot string handling References: <1392143619-11453-1-git-send-email-paul.gortmaker@windriver.com> <20140212020010.GB21033@windriver.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [128.224.146.65] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14-02-11 09:23 PM, David Rientjes wrote: > On Tue, 11 Feb 2014, Paul Gortmaker wrote: > >>>> Fixes: >>>> >>>> arch/x86/boot/compressed/../string.c:60:14: warning: symbol 'atou' was not declared. Should it be static? >>>> arch/x86/boot/string.c:133:6: warning: symbol 'strstr' was not declared. Should it be static? >>>> >>>> The atou one could be considered a false positive; it seems somehow >>>> caused by including ./string.c from within /compressed/string.c file. >>>> However git grep shows only the atou prototype and declaration, so >>>> it is completely unused and we can hence delete it. >>>> >>> >>> Declaring a prototype in a header file would be pointless if there is no >>> current breakage; I don't see why you can't remove strstr() in >>> arch/x86/boot/string.c entirely. What breaks? >> >> Explicit breakage vs. sparse warnings are two different things. It may >> be that we can delete strstr() just like I did for atou() -- but in the >> interest of doing the minimal change, I did just what was needed for >> fixing the sparse warnings for strstr. I can test if it can be removed, >> but it has the smell of generic-libc usage all over it... >> > > When the minimal change is to add an unnecessary prototype for a function > that is not referenced, it doesn't seem acceptable. OK, fair enough -- it seems surprisingly unused, as well as strcmp, despite my gut feeling that they'd be used in multiple places. I'll send a v2 that deletes all three once it passes allyesconfig on linux-next for x86 32/64/uml. Thanks, Paul. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/