Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936843Ab3DIHwx (ORCPT ); Tue, 9 Apr 2013 03:52:53 -0400 Received: from mail-ie0-f173.google.com ([209.85.223.173]:35113 "EHLO mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935258Ab3DIHww (ORCPT ); Tue, 9 Apr 2013 03:52:52 -0400 MIME-Version: 1.0 In-Reply-To: <1363674681-4015-1-git-send-email-sachin.kamat@linaro.org> References: <1363674681-4015-1-git-send-email-sachin.kamat@linaro.org> Date: Tue, 9 Apr 2013 09:52:51 +0200 Message-ID: Subject: Re: [PATCH 1/5] pinctrl: abx500: Staticize some symbols From: Linus Walleij To: Sachin Kamat Cc: "linux-kernel@vger.kernel.org" , Patch Tracking , Patrice Chotard Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1278 Lines: 29 On Tue, Mar 19, 2013 at 7:31 AM, Sachin Kamat wrote: > These symbols are used only in this file. Without this patch > we get the following warnings: > drivers/pinctrl/pinctrl-abx500.c:520:5: warning: > symbol 'abx500_gpio_request' was not declared. Should it be static? > drivers/pinctrl/pinctrl-abx500.c:527:6: warning: > symbol 'abx500_gpio_free' was not declared. Should it be static? > drivers/pinctrl/pinctrl-abx500.c:614:5: warning: > symbol 'abx500_gpio_request_enable' was not declared. Should it be static? > drivers/pinctrl/pinctrl-abx500.c:714:5: warning: > symbol 'abx500_pin_config_get' was not declared. Should it be static? > drivers/pinctrl/pinctrl-abx500.c:721:5: warning: > symbol 'abx500_pin_config_set' was not declared. Should it be static? > > Signed-off-by: Sachin Kamat > Cc: Patrice Chotard > --- > This series is compile tested against linux-next tree (20130319). Patch applied with Patrice's ACK, thanks! Yours, Linus Walleij -- 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/