Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753877AbbG0Plu (ORCPT ); Mon, 27 Jul 2015 11:41:50 -0400 Received: from mail-oi0-f48.google.com ([209.85.218.48]:33844 "EHLO mail-oi0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbbG0Pls (ORCPT ); Mon, 27 Jul 2015 11:41:48 -0400 From: Rob Herring To: Tomi Valkeinen Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, Nicolas Ferre , Jean-Christophe Plagniol-Villard Subject: [PATCH] video: fbdev: atmel: fix warning for const return value Date: Mon, 27 Jul 2015 10:41:41 -0500 Message-Id: <1438011701-18423-1-git-send-email-robh@kernel.org> X-Mailer: git-send-email 2.1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1378 Lines: 38 A const on a return value is meaningless and generates a warning on some versions of gcc: drivers/video/fbdev/atmel_lcdfb.c:1003: warning: type qualifiers ignored on function return type This was found on 0-day with avr32 builds with CONFIG_OF enabled, but it doesn't seem to generate warnings for other arches. Reported-by: Fengguang Wu Signed-off-by: Rob Herring Cc: Nicolas Ferre Cc: Jean-Christophe Plagniol-Villard Cc: Tomi Valkeinen --- drivers/video/fbdev/atmel_lcdfb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/atmel_lcdfb.c b/drivers/video/fbdev/atmel_lcdfb.c index abadc49..66f4b70 100644 --- a/drivers/video/fbdev/atmel_lcdfb.c +++ b/drivers/video/fbdev/atmel_lcdfb.c @@ -999,7 +999,7 @@ static const char *atmel_lcdfb_wiring_modes[] = { [ATMEL_LCDC_WIRING_RGB] = "RGB", }; -const int atmel_lcdfb_get_of_wiring_modes(struct device_node *np) +int atmel_lcdfb_get_of_wiring_modes(struct device_node *np) { const char *mode; int err, i; -- 2.1.0 -- 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/