Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753502AbbGPNbm (ORCPT ); Thu, 16 Jul 2015 09:31:42 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:33349 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751677AbbGPNbk (ORCPT ); Thu, 16 Jul 2015 09:31:40 -0400 MIME-Version: 1.0 In-Reply-To: <55A79EFD.3050100@gmail.com> References: <1436042072-7496-1-git-send-email-xerofoify@gmail.com> <55A79EFD.3050100@gmail.com> From: Alexandre Courbot Date: Thu, 16 Jul 2015 22:31:21 +0900 Message-ID: Subject: Re: [PATCH] gpio:Fix build warning about void to integer cast in the function mmio_74xx_gpio_probe To: nick Cc: Linus Walleij , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1754 Lines: 42 On Thu, Jul 16, 2015 at 9:09 PM, nick wrote: > > > On 2015-07-16 08:00 AM, Linus Walleij wrote: >> On Sat, Jul 4, 2015 at 10:34 PM, Nicholas Krause wrote: >> >>> This fixes the build warning , warning: cast from pointer to integer >>> of different size when building this file on a x86 allmodconfig >>> configuration. In order for me to fix this build warning I changed >>> the cast in the function mmio_74xx_gpio_probe from casting the >>> variable data of the stucture pointer of_id to uintptr_t rather >>> then unsigned when assigning to the variable flag of the structure >>> pointer priv of the structure type mmio_74xx_gpio_priv. >>> >>> >>> Signed-off-by: Nicholas Krause >> >> Patch applied with some tweaks to the long subject line. >> >> Yours, >> Linus Walleij >> > Sorry about that I kinda suck at commit messages if you would like to some me the edit > so I can get better at it, that would be helpful. As explained in Documentation/SubmittingPatches: (probably a good idea to re-read that document) "For these reasons, the "summary" must be no more than 70-75 characters, and it must describe both what the patch changes, as well as why the patch might be necessary. It is challenging to be both succinct and descriptive, but that is what a well-written summary should do." Your patch subject line should not be longer than 70-75 characters. If you need to be more extensive, do so in the first paragraph of your commit log. -- 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/