Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759969AbcCDUzW (ORCPT ); Fri, 4 Mar 2016 15:55:22 -0500 Received: from nm2-vm6.bullet.mail.ir2.yahoo.com ([212.82.96.86]:58434 "EHLO nm2-vm6.bullet.mail.ir2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758341AbcCDUzV (ORCPT ); Fri, 4 Mar 2016 15:55:21 -0500 X-Greylist: delayed 382 seconds by postgrey-1.27 at vger.kernel.org; Fri, 04 Mar 2016 15:55:21 EST X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 91656.6719.bm@omp1026.mail.ir2.yahoo.com X-YMail-OSG: dKl_vXQVM1mcnt1_SBs_ZjHqFGeXPJlBfCpr2s5dW8SRDh_jyFyGEJoe4rQ9W9w 3Yhe2cbfINhA2NHCli94GSJYvv3o609wuSFskffbkrXOllGqI4Bj2Yli_5GY76RWphoM7ugA2y5M zGvVRd8uH5i9Fn7kFk63.rjtlmzXfkiCSGJajcvmmzi9pLKHHtytjfpE9t3fusnFNNlp_z8_RApI l4DJ8fyHGsBIp0I4u4ohEPNcygmMju1b7l3vITXt9kw7AGwIor0sNTUAu1U8ncKt3s1gR5vPgPvM aR6YhPKVAgVOu9HBzYFdZIkJdBnq0B1CCzrLPDmFHRAhosR2dnUtH_23dM_mUN.KmX4iTGf2sprh kOhTYQVslUCH4..l_.iJDyB9NddQRmlb7vUNwV__kSvyx7YjrHxwtJUBfeBBHXFyW3Cm6HV1GM2W P8_WOqnNgg1aMy2i_3c6cHY2ZgnCiQG7dDUkRAE855MN2LORXRwtYvr09gt2_eiuRrpHP8D25d8x X24wadVJQCDbzyuJ4HzBgADuq_60wBvCG8YKo9A-- Date: Fri, 4 Mar 2016 20:48:56 +0000 (UTC) From: Gianfranco Costamagna Reply-To: Gianfranco Costamagna To: Arnd Bergmann Cc: "linux-kernel@vger.kernel.org" , "trivial@kernel.org" Message-ID: <947317636.5681951.1457124536330.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <5693177.gLSTqHZso3@wuerfel> References: <5693177.gLSTqHZso3@wuerfel> Subject: Re: [PATCH] ARM: LLVMLinux: Change "extern inline" to "static inline" in mpi-inline.h and mpi-internal.h MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2458 Lines: 70 Hi >Close, but not quite right. >It's currently in the crypto tree after Herbert Xu picked it up. >It is scheduled to be merged into 4.6 at the moment. wonderful, sure, in the next merge window is good. But there is a little difference between your patch and mine. In your case they were build warnings, now with gcc-5 as default (e.g. Debian, Ubuntu), they are errors, so I would give the patch merge a speedup... but who am I to give suggestions to kernel folks? :) I can use the patch locally, and wait for the next release (actually I'm using it on iMX6 machines, so I have to backport this kind of patches anyway) >The mail is not formatted in a way that allows being imported with >'git am'. The best way to do this right is to use the headers >as they come from git format-patch directly, and start the mail with >the changelog text (and with a From: line before that). I did a git format-patch -1 commitid, from the source tree. The mail client (Thunderbird) has been configured with the documentation in the source tree, but I think it failed to not wrap the lines :) (I also have used git send-email or something similar some months ago, maybe I could have just used it) >Here you have kept my Signed-off-by line, but not the author attribution. >This is easy to get wrong. You probably want to change the author >field using 'git commit --amend --author="Arnd Bergmann "', >which will cause the correct From: line to show up when exporting it >with git send-email. I know really good git, but I left it that way, because actually the patch was different from your one, and I don't want people blaming you instead of me. (not sure if the right approach, I thought the signoff was something nice, but probably I agree it is even worse) >You have marked the function as 'static' here, rather than 'static inline' >as I did in my patch. I think my version is better here, because it matches >the definition of the function, and because declaring a function as >'static' in a header file is generally a bad idea: you will get a build >warning or error if the header is included in a file that does not provide >a definition. true story, bad copy paste from commits aeea3592a13bf12861943e44fc48f1f270941f8d 76ae03828756bac2c1fa2c7eff7485e5f815dbdb I'll try to make it right the next time! thanks for the explanation, I patch kernel almost daily, I hope to contribute to it in the near future. cheers, Gianfranco