From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751885AbcDZNI1 (ORCPT ); Tue, 26 Apr 2016 09:08:27 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:21719 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbcDZNIZ (ORCPT ); Tue, 26 Apr 2016 09:08:25 -0400 To: Arnd Bergmann Cc: James Bottomley , "Martin K. Petersen" , Josh Poimboeuf , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, Denys Vlasenko , Thomas Graf , Peter Zijlstra , David Rientjes , Andrew Morton , jamborm@gcc.gnu.org, Ingo Molnar , Himanshu Madhani , qla2xxx-upstream@qlogic.com Subject: Re: [PATCH] scsi: fc: force inlining of wwn conversion functions From: "Martin K. Petersen" Organization: Oracle Corporation References: <20160419085221.GA29087@gmail.com> <1461641851.2392.32.camel@HansenPartnership.com> <5249561.9VpAPLD61M@wuerfel> Date: Tue, 26 Apr 2016 09:06:54 -0400 In-Reply-To: <5249561.9VpAPLD61M@wuerfel> (Arnd Bergmann's message of "Tue, 26 Apr 2016 09:22:46 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Source-IP: aserv0022.oracle.com [141.146.126.234] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "Arnd" == Arnd Bergmann writes: Arnd> I don't think we can realistically blacklist gcc-4.9.{0,1,2,3}, Arnd> gcc-5.{0,1,2,3}.* and gcc-6.0 and require everyone to upgrade to Arnd> compilers that have not been released yet in order to build a Arnd> linux-4.6 kernel. I agree that compiler blacklisting is problematic and I'd like to avoid it. The question is how far we go in the kernel to accommodate various levels of brokenness. In any case. Sticking compiler workarounds in device driver code is akin to putting demolition orders on display on Alpha Centauri. At the very minimum the patch should put a fat comment in the code stating that these wrapper functions or #defines should not be changed in the future because that'll break builds using gcc XYZ. But that does not solve the problem for anybody else that might be doing something similar. Converting between u64 and $RANDOM_TYPE in an inline wrapper does not seem like a rare and unusual programming pattern. -- Martin K. Petersen Oracle Linux Engineering